4 Replies Latest reply on Apr 26, 2013 6:05 AM by jaikiran pai

    Reconnect to remote JMS / TopicConnection after reboot EAP 6.0.1.GA

    sameer shukla Newbie

      I am using JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) & I have a plain java client which invoke APIs of EJB using JNDI & receive  the responses over JMS queue.

       

      When ever the JBoss is restarted & my client tries to relookup the destination using the InitialContext but following exception is received :

       

      org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is org.jboss.remoting3.NotOpenException: Writes closed]

              at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:49)

              at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:104)

              at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:79)

              at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)

              at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)

              at javax.naming.InitialContext.lookup(InitialContext.java:392)

       

      This issue seems to be same as https://issues.jboss.org/browse/AS7-4508 but the workaround suggested in there to include the 1.0.4.Final-SNAPSHOT version of jboss-remote-naming jar in jboss client classpath doesnt work for me.

       

      And I cannot upgrade my JBoss version due to project mgmt related decision.

       

      Is there any other workaround for my issue like new updated jboss-client.jar with the fix of jboss-remoting-naming in it & which is compatible with JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4).

       

       

      Thanks