I am using an outbound-gateway and reply-listener with Tibco EMS. If EMS is bounced the outbound-gateway and reply-listener reconnect perfectly fine. However, if a request occurs while the there is a network disconnect (e.g. I unplug the ethernet cable from my EMS server) the outbound-gateway seems to recover and resume sending messages but the reply-listeners does not consistently do so. When the reply-listener fails to realize it has been disconnected, the result is the outbound-gateways sending requests with reply to destination that no longer exists. Thus all requests timeout. Interestingly, not only will bouncing the client correct this situation, but so will bouncing EMS.
If I remove the reply-listener and allow the outbound-gateway to create a new reply to destination with every request then recovery is very consistent.
Does anyone have any ideas about how this may be overcome, outside of removing the reply-listener?
The offending outbound-gateway:
If I remove the reply-listener and allow the outbound-gateway to create a new reply to destination with every request then recovery is very consistent.
Does anyone have any ideas about how this may be overcome, outside of removing the reply-listener?
The offending outbound-gateway:
Code:
<int-jms:outbound-gateway request-channel="requestChannel" correlation-key="JMSCorrelationID"
request-pub-sub-domain="true" request-destination-name="polo"
connection-factory="poloConnectionFactory" explicit-qos-enabled="true"
time-to-live="5000" receive-timeout="5000">
<int-jms:reply-listener/>
</int-jms:outbound-gateway>