3 Replies Latest reply on May 11, 2005 2:37 AM by henk s

    client cannot reconnect after server restart

    henk s Newbie

      Hi,

      I have a jms client program that runs as a daemon. In order to survive a jboss restart, I used the ExceptionListener. All the jndi stuff is in a helper class, which is used by the client. When an exception is encoutered, the helper notifies the client and the client closes all connections and sessions and tries to reestablish the connection after a few minutes. However, when doing this, I get this exception :

      javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table]
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:647)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
      at javax.naming.InitialContext.lookup(InitialContext.java:347)
      at be.kmi_irm.labo.messaging.jms.JMSConnectionHelper.initConnection(JMSConnectionHelper.java:71)
      at be.kmi_irm.labo.messaging.jms.OAQ2JMSForwarder.initJMS(OAQ2JMSForwarder.java:92)
      at be.kmi_irm.labo.messaging.jms.OAQ2JMSForwarder.onJMSException(OAQ2JMSForwarder.java:154)
      at be.kmi_irm.labo.messaging.jms.JMSConnectionHelper.onException(JMSConnectionHelper.java:142)
      at org.jboss.mq.Connection.asynchFailure(Connection.java:439)
      at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:145)
      at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:398)
      at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:332)
      at java.lang.Thread.run(Thread.java:534)
      Caused by: java.rmi.NoSuchObjectException: no such object in table
      at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
      at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
      at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
      at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528)
      ... 11 more


      Although jboss is again up , apparantly the jndi lookups fail. What could cause this ? If I restart the client everything is fine again.
      I am using jboss 4.0 .

      Thanks,

      Henk