Cache Large Messages on Client
23.5. Cache Large Messages on client Large messages are transferred by streaming from server to client. The message is broken into smaller packets and as the message is read more packets will be received. Because of that the body of the large message can be read only once, and by consequence a received message can be sent to another producer only once. The JMS Bridge for instance won't be able to resend a large message in case of failure To solve this problem, you can enable the property cache-large-message-client on the connection factory. If you enable this property the client consumer will create a temporary file to hold the large message content, so it would be possible to resend large messages. Note Use this option on the connection factory used by the JMS Bridge if the JMS Bridge is being used for large messages.