users@glassfish.java.net

Re: Detecting A Broken JMS Connection/Session/Destination Link and Reconnecting

From: rdblaha1 <rd_blaha_at_hotmail.com>
Date: Tue, 25 Mar 2008 06:51:42 -0700 (PDT)

I was pulled to other work for a while so I did not keep on this, but now I
need to ask the question again. What are feasible methods for specifically
detecting whether my JMS Connection is no longer valid, my Session is no
longer valid, or my Destination is no longer valid.

I have learned by experience that if I set up Queue1 with the property
name=queue and Queue2 with the property name=queue with the AppClient on the
client side with NO connection to Queue1 and Queue2 on the appserver that my
consumer on my appclient will read from the output of my producer on my
appclient. Also, my producer was satisfied (acknowledge returned within the
'send.producer' command) that the message had reached the actual destination
on the appserver.

Because of this I am looking for these specific tools rather than simply
detecting if the network is still connected from appclient to appserver.

Please help me. Thank you.

-- 
View this message in context: http://www.nabble.com/Detecting-A-Broken-JMS-Connection-Session-Destination-Link-and-Reconnecting-tp15746362p16274783.html
Sent from the java.net - glassfish users mailing list archive at Nabble.com.