Reconnecting to J2EE server

Question

I am developing a Adapter in TIBCO which connects to a J2EE server which acts a
host for JMS queue. This adapter picks up the the messages from the JMS queue
and publishes on the TIBCO bus.
Now JMS subscribers receive messages through a registration - callback
mechanism. If the J2EE server hosting the JMS queue goes down the subscriber is
not notified and simply receives no messages. In the jms adapter this means
that when the weblogic (J2EE) server comes back up no messages are received as
subscriber configurations have been lost on the server side.
To work around this we need to implement a disconnect-connect operation after
the adapter has been idle for a certain length of time using a separate timer
thread. But when i try to reconnect to the J2EE server after it starts again an
exception is raised.
This is code snippet i am using for reconnection. It is pretty straight forward.
try {
context = new InitialContext ();
          catch (NamingException nm)
               System.out.println ("NamingException " + nm);
          try {
               queueconnectionfactory = (QueueConnectionFactory)
context.lookup(queueConnectionFactoryName);
queueconnection =
queueconnectionfactory.createQueueConnection();
               queuesession = queueconnection.createQueueSession(false,
Session.AUTO_ACKNOWLEDGE);
               queue = (Queue) context.lookup(subJMSQueue);
queuereceiver = queuesession.createReceiver(queue);
queuereceiver.setMessageListener (listener);
queueconnection.start();
                                   outQueue = (Queue) context.lookup(pubJMSQueue);
                    catch (NamingException ne) {
                    System.out.println ("ERROR: Error while JNDI Namespace look up. Reason: " +
ne.toString());
               try {
               queueSender = queuesession.createSender(outQueue);
               catch (JMSException je) {
                    System.out.println ("ERROR: Error while creating Queue Objects. Reason: " +
je.toString());
          catch (NamingException ne)
               System.out.println ("Fatal! Initialization of JMS adapter failed - Could not
obtain connection objects for the JMS queue." + ne);
          catch (Exception e)
               System.out.println ("Fatal! Initialization of adapter failed - Could not
obtain components from registry." + e);
This is the exception i am getting.
javax.naming.CommunicationException: java.rmi.MarshalExcepti
on: CORBA COMM_FAILURE 1398079689 No; nested exception is:
org.omg.CORBA.COMM_FAILURE: minor code: 1398079689 completed: No
org.omg.CORBA.COMM_FAILURE: minor code: 1398079689 completed: No
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(Connecti
onTable.java:176)
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(Connecti
onTable.java:68)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:7
0)
at com.sun.corba.ee.internal.corba.ClientDelegate.createRequest(ClientDe
legate.java:641)
at com.sun.corba.ee.internal.corba.ClientDelegate.createRequest(ClientDe
legate.java:583)
at com.sun.corba.ee.internal.corba.ClientDelegate.request(ClientDelegate
.java:875)
at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:433)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lo
okup(Unknown Source)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:120
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at com.hutchison3g.core.ea.adapter.jmsadapter.JMSReconnectionTimer.reest
ablishJMSConnection(JMSReconnectionTimer.java:117)
at com.hutchison3g.core.ea.adapter.jmsadapter.JMSReconnectionTimer.onEve
nt(JMSReconnectionTimer.java:42)
at com.tibco.sdk.events.EventHandoff.run(MEventSource.java:141)
at java.lang.Thread.run(Thread.java:484)
Any suggestion whether i am doing it correct or how else can i do this.
Thanks all in advance.

Answer 1

The classic way to sort this kind of connectivity issue out is to use JINI.
JINI provides you with facilities that allow for the publication of services over a network. It also provides with facilities for discovering which services are currently available and which are not. It also does a tonne of other things for you too, including having invented this particular wheel for you.
In your case you would be introducing a rapdily emerging but mature system into your application that you will probably find a 1000 other uses for.
I find JINI fascinating to work with, I hope you do too (its a cannot live without it experience for me now)