Camel JMS streaming

Question

I have an application that posts a message in JMS Queue. Message size can be up to 150 mb. The JMS message contains byte array data with additional metadata in the form of xml, as soon as the message is queued, the camel route application selects the message and calls an external java-api with the message. I would like to pass a message from the JMS queue using the camel arrow component. Could you tell me if I can achieve this with a camel. I am currently facing a heap error issue.

An example JMS message is shown below.

<request> <esb-metadata> <source-transaction-id>1234567890</source-transaction-id> <environment>Dev</environment> <message-type>REQ</message-type> <source-id>12345678</source-id> <master-id>mst-id1234</master-id> </esb-metadata> <message-body> <parameters> <info> <document-class>Document</document-class> <document-guid>idd_C0A5DF59-0000-C51C-BCDA-E76E9476D5C2</document-guid> </info> </parameters> <document> <document-mime-type>std/text</document-mime-type> <document-content>SGVhZGluZzEgQ2hhbmdlZCB0b2RheSBKYW4gMTEgc2FtcGxlIHRleHQgYmVsb3csDQpPbmNlIEkg cmVjZWl2ZSB0aGlzIGluZm9ybWF0aW9uLCBJIHdpbGwgdGhlbiBjb250YWN0IHlvdSBpbW1lZGlh dGVseSB0byBkaXNjdXNzIHRoZSByZXNvbHV0aW9uIG9mIHlvdXIgY2xhaW0uDQoNCg0KSGVhZGlu ZzIgc2FtcGxlIHRleHQsDQpJZiBwb3NzaWJsZSwgSSBuZWVkIHRvIHJlY2VpdmUgdGhpcyBpbmZv cm1hdGlvbiBmcm9tIHlvdSB3aXRoaW4gMzAgRGF5cy4NCg0KMQkxCTENCjIJMgkyDQozCTMJMw0K NAk0CTQNCg0KSGVhZGluZzMgc2FtcGxlIHRleHQsDQpJIHdpbGwgYXNzdW1lIHlvdSBkbyBub3Qg d2lzaCB0byBwdXJzdWUgdGhpcyBjbGFpbSBhbmQgSSB3aWxsIGNsb3NlIG15IGZpbGUuDQpBRERF RCBUSElTIE5FVyBMSU5FIFRPIFNFRSBJRiBJVCBJUyBWSVNJQkxFDQoNCnRhYmxlIHN0YXJ0cyBo ZXJlDQpwb2xpY3kgbnVtYmVyCWNsYWltIG51bWJlcglpbnN1cmVkDQpwMTIzCWMxMjMJYm9zY2gN CnAzMjEJYzMyMQlibXcNCnRhYmxlIGVuZHMgaGVyZQ0KDQomIzk2Nzk7CUJ1bGxldCBwb2ludCAx DQomIzk2Nzk7CUJ1bGxldCBwb2ludCAyDQomIzk2Nzk7CUJ1bGxldCBwb2ludCAzDQoNCjEuCU51 bWJlcmVkIHBvaW50IDENCjIuCU51bWJlcmVkIHBvaW50IDINCjMuCU51bWJlcmVkIHBvaW50IDMN Cg== </document-content> </document> </message-body> </request> 

Answer 1

HornetQ supports streaming large messages so customers don’t have to worry about hitting memory limits. This support works in the JMS HornetQ implementation, but the JMS API does not support the direct transmission of large messages, so the standard JMS component (for example, the one provided by Camel) will probably not work for this use case. You will need to use a component written to support the implementation of HornetQ. You can read about how HornetQ JMS clients can send large messages to documentation .