Issue

• I attempted to raise the min-large-message-size limit to 200 Kb. I did so on all connection factories, and that provides the appropriate result except when messages are sent through the cluster connection to the other member. when that happens, messages are treated based on the default min-large-message-size, which is 100 Kb.
• The end result is that when we send 2 messages, because of the server side load balancing, one message is stored as a normal message and one is a large message.It sounds that we should be able to express min-large-message-size on cluster-connection as well.