21.5. Cache Large Messages on client

Large messages are transferred from server to client by streaming. The message is broken into smaller packets and more packets will be received as the message is read. It is because of this 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 will not be able to resend a large message in case of failure.

To solve this problem, you can enable the property cache-large-message-client in 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.