Strange behaviour in Exception delivery for JMS connection

[mohammad abdellatif]

hi,
I am connecting to Websphere application server version 6.0, I am using an ExceptionListener to make use from API notification when the connection between my application and application server is broken to recover my connection:

 
public class MyExceptionListener implementeds ExceptionListener{
       public void onException(JMSException ex){
             // do connection recovery here
       }
}
 

I used this technique before in other MQ providers like Sun Message Queue and IBM MQSeries, I was notified only one when the connection is broken.

But when I am connected to Websphere, I will be notified three times. do any body knows why this behavious happens? how I am going to make it called only once. Below is my sample test and the output for it:

FYI: What I am doing to test this case is shutting down application server using stopServer.sh command

package test;

import java.util.Date;
import java.util.Hashtable;

import javax.jms.ConnectionFactory;
import javax.jms.ExceptionListener;
import javax.jms.JMSException;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.swing.JFrame;

public class Test2 {
	public static int COUNT = 0;

	public static void main(String[] args) throws Exception {
		Hashtable env = new Hashtable();

		env.put(Context.INITIAL_CONTEXT_FACTORY,
				"com.ibm.websphere.naming.WsnInitialContextFactory");
		env.put(Context.PROVIDER_URL, "iiop://172.18.10.21:2811/");
		env.put(Context.SECURITY_AUTHENTICATION, "");
		env.put(Context.SECURITY_PRINCIPAL, "");
		env.put(Context.SECURITY_CREDENTIALS, "");
		System.out.println("==>>lookup for a new factory");
		InitialContext context = new InitialContext(env);

		ConnectionFactory factory = (ConnectionFactory) context
				.lookup("CIS_QCF");
		System.out.println(factory.getClass().getName());
		javax.jms.Connection connection = factory.createConnection();
		connection.setExceptionListener(new ExceptionListener() {

			public void onException(JMSException arg0) {
				System.out.println("inside onException: " + COUNT++);
				System.out.println("code: " + arg0.getErrorCode()
						+ "\nmessage: " + arg0.getMessage()
						+ "\nlocalizedMessage: " + arg0.getLocalizedMessage()
						+ "\ncause: " + arg0.getCause());				
				System.out.println("=========================");
			}
		});
		System.out.println("==>>this is called successfull");
		
	}
}

output is:

 
==>>lookup for a new factory
com.ibm.ws.sib.api.jms.impl.JmsQueueConnectionFactoryImpl
Nov 8, 2009 11:22:49 AM com.ibm.ws.sib.utils.ras.SibMessage
WARNING: SIB_MESSAGE
Nov 8, 2009 11:22:49 AM com.ibm.ws.channel.framework.impl.WSChannelFrameworkImpl
AUDIT: chain.started
==>>this is called successfull
inside onException: 0
code: CWSIA0344
message: CWSIA0344E: The connection has been closed because the messaging engine has terminated.
localizedMessage: CWSIA0344E: The connection has been closed because the messaging engine has terminated.
cause: null
=========================
inside onException: 1
code: CWSIA0342
message: CWSIA0342E: The messaging engine is shutting down.
localizedMessage: CWSIA0342E: The messaging engine is shutting down.
cause: null
=========================
inside onException: 2
code: CWSIA0343
message: CWSIA0343E: The connection has been closed because of the following exception: com.ibm.ws.sib.jfapchannel.JFapConnectionBrokenException: CWSIJ0056E: An unexpected condition caused a network connection to close.
localizedMessage: CWSIA0343E: The connection has been closed because of the following exception: com.ibm.ws.sib.jfapchannel.JFapConnectionBrokenException: CWSIJ0056E: An unexpected condition caused a network connection to close.
cause: com.ibm.ws.sib.jfapchannel.JFapConnectionBrokenException: CWSIJ0056E: An unexpected condition caused a network connection to close.
=========================