We are encountering a new situation. When we want to send a sync message to JMS using pub.jms:sendAndWait, the response ends up in DLQ. However, it ends there even before timeout has expired (60 sec).
Note: we’re running on two ISs on cluster, one broker. Sometimes, the IS service that invokes pub.jms:sendAndWait is running on one node of the cluster and the receiving on another.
Any idea, why the JMS is not capable of putting the response back and pushes it to DLQ?