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

[samshukla12]

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

[jaikiran]

Sameer, welcome to the forums.

Are you a paid customer of JBoss EAP? If you are, then you are entitled to support from the support team for EAP 6.0.1. Please use the support portal so that they can help you with the issue and maybe provide a patch if it's a bug.

If you are not a paid customer, then I would recommend that you use the latest released version from here http://www.jboss.org/jbossas/downloads and see if this issue is fixed there. If you have any questions related to these newer versions, feel free to ask here.

[jaikiran]

sameer shukla wrote:

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

I didn't notice this earlier.

So in that case, you will have to make sure you have really upgraded the client classpath with the newer remote-naming jar. How did you "upgrade" it?

[samshukla12]

Hi Jaikiran,

Thanks for quick reply.

I just added the remote-naming jar to my client classpath along with my jboss-client jar.

But jboss-client jar contains classes which are present in remote-naming jar, so shall I make an custom jboss-client jar by repacing old classes with new ones from this remote-naming jar.

Thanks

[jaikiran]

sameer shukla wrote:

I just added the remote-naming jar to my client classpath along with my jboss-client jar.

That won't work.

sameer shukla wrote:

Hi Jaikiran,

But jboss-client jar contains classes which are present in remote-naming jar, so shall I make an custom jboss-client jar by repacing old classes with new ones from this remote-naming jar.

Yes, that exactly what you have to do. You have to rebuild the jboss-client.jar with the newer version of remote-naming classes.