How can a remote jms receiver detect loss of connection to Messaging server

Question

Plan:
Messaging server (like JbossMQ /SonicMQ) is hosted on one machine.
A JMS receiver (MDB/core java program) on another machine receives messages from the messaging server.
Secnario:
The JMS receiver is now continuously listening or occasionally reading messages from a certain queue of the server using a JMS connection.
Now the messaging server has this receiver in its list of receivers for that particular queue.
For some reason the messaging server is down and then restarted.
The JMS connection of the receiver is now invalid.
When the messaging servers comes up again its list of receivers is empty.
Required Solution:
Can you please help me on how the JMS receiver can detect the above scenario and re-establish the connetion to the messaging server, the next time the server is up.
Observations:
When I create a message consumer or queue receiver in a j2se program, and take messages from JbossMQ I have some additional threads running on my JVM. These threads are not directly created by the program and servers only for receiving messages. One of these threads is catching an exception and printing a stack trace when it detects that the connection is lost. This will also result in the closing of JMS connection. The problem is that the exception is not thrown for the programmer to catch and handle it at some level. I also tried ExceptionListener and waited for ping interval. Is there a concept of receiver listening to the periodic heart beat of the server. Please give me guidance, solutions or corrections.
For comments on this, Thanks in advance

Answer 1

Hi Leendert,
do you want to use the JMS API directly? In this case you have to create the connection factory on system X. From system Y, you access the JNDI on system X and look up the connection factory. Since you are accessing the JNDI on system X from outside, you need to set some properties to create the InitialContext:
    Properties env = new Properties();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
    env.put(Context.PROVIDER_URL, <system X>:<p4 port>); // replace with your settings
    env.put(Context.SECURITY_PRINCIPAL, <user name>); // replace with your settings
    env.put(Context.SECURITY_CREDENTIALS, <password>); // replace with your settings
    naming = new InitialContext(env);
Hope that helps.
Regards,
Sabine