Hi team, We have a 2-node symmetric cluster. Producer writes on node1, and consumer consumes from node2. As the clustering is working fine, messages move from node1 to node2 for consumer. So far, the setup is working fine.
One of our producers started writing larger custom JMS header to pass stack trace information. Producer is able to write the message to node1 but it is not being moved to node2 via clustering. Seems it gets stuck in the clustering queue and does not move from node1 to node2. Once a message gets stuck in clustering queue, other messages with or without large JMS headers also get stuck and no message is delivered to node2 via clustering. Is there any restriction in custom JMS header size or total accumulative JMS headers size? Since we can write the message with large custom JMS header at node1, if there is any restriction in clustering which is not allowing message movement inside cluster due to presence of large JMS header? Thanks Shiv
