Issue

• When more than two instances of either EAP or SOA-P are used in combination with core bridges connecting queues of one instance to other queues in another instance, it can happen that JMS text messages which are sent as "non-large" messages can become "large" when they are persisted on a middle node and then redistributed to another node. In that case, the receiving node will get null when calling getText() on the message.
• The problem occurs for text messages whose text body is between 51149 and 51200 characters long when the default min-large-message-size of 102400 is used.
• If a different min-large-message-size was used then the body length range which triggered the problem would shift.