onException is called when the connection is lost, as you discovered.
Set a flag to tell your 'main loop' (term use loosely) to
reconnect. Don't try to re-use it. I retry the connection
every 30 sec or so in my consumers...
-----Original Message-----
From: Michael Nonemacher [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 10, 2001 10:36 AM
To: [EMAIL PROTECTED]
Subject: [developers] guaranteed-delivery problem with intermittent
network
I have a simple testcase that involves 2 VMs sending messages to each other.
The testcase sends a few message from A to B, which causes a few messages to
get sent from B to A. This part works fine. The next part of the testcase
involves shutting down the network, sending a few more messages from A to B,
then restarting the network and ensuring that the messages are eventually
delivered.
When I stop the network, I get the following exception delivered to my
ExceptionHandler:
javax.jms.JMSException
at com.swiftmq.jms.ConnectionImpl.run(ConnectionImpl.java:458)
at java.lang.Thread.run(Thread.java:484)
Restarting the network doesn't cause the messages to get delivered, and
connection.stop() throws a javax.jms.IllegalStateException (Connection is
closed).
What can I do in my ExceptionHandler to make sure the connection is usable
again once the network returns, and someone can exit my app before then?
mike
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/[email protected]/
------------------------------------------------------ SwiftMQ developers mailing list * http://www.swiftmq.com To unsubscribe from this list, send an eMail to [EMAIL PROTECTED] and write in the body of your message: UNSUBSCRIBE developersArchive: http://www.mail-archive.com/[email protected]/
