You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Len Takeuchi <lt...@salescentrix.com> on 2005/03/03 02:55:45 UTC

JMS Transport and Connection Fault-Tolerance

Hi,

I'm using Axis 1.2 and using JMS as the transport using Queues.  When
connection to the JMS is dropped, connection is automatically re-established
and the processing continues without a problem.  I was looking through the
JMS transport code and I noticed that in the onException method for
AsyncConnection in org.apache.axis.transport.jms.JMSConnector.java, all it's
doing is in the list of 'Subscription's maintained for the connection, it
clears out the session associated with each Subscription.  I thought that
code to re-establish connection would be there but it is not.  In the
onConnect method, for those Subscriptions without associated session,
creates a session and sets up the listener.  What I cannot figure out is
what is causing the connection to be re-established when the connection is
dropped.  Since the JMS provider (Sonic) we are using does have support for
fault tolerant connections, I thought that maybe being configured at a
vendor specific level but it doesn't seem like it.  If someone knows which
code or what is causing the re-connect to occur, I would appreciate it.

Regards,
Len Takeuchi
Salescentrix.com