java.lang.NullPointerException at org.jboss.jms.client.conta

[dejanb]

Hi,

We have an application that uses a cluster (from the JBoss AS server point of view all servers are standalone but we have our own clustering) of JBoss 5.0 servers and a single JBoss 5.0 server that only deploys JBM 1.4.1.GA .

Everything works fine if the JBM service is deployed on all JBoss servers and connecting to the standalone JBM server.

However removing the JBM service causes the exception below to be thrown on connect:

java.lang.NullPointerException
at org.jboss.jms.client.container.ConnectionAspect.getConnectionState(ConnectionAspect.java:252)
at org.jboss.jms.client.container.ConnectionAspect.handleSetExceptionListener(ConnectionAspect.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.setExceptionListener(ClientConnectionDelegate.java)
at org.jboss.jms.client.JBossConnection.setExceptionListener(JBossConnection.java:116)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

I searched and found a couple of issues related to deployment isolation but I don't think these apply in our case because of the version we use.

The classpath doesn't change between runs so it's probably not the cause of the issue either.

Thanks for your help,
Deyan

[gaohoward]

Hi,

How do you remove the JBM service? which JBM service did you remove, the 'standalone' one or the others?

I'm a bit confused so please give more detail, thanks.

[dejanb]

The "standalone" JBM service is always deployed and that server is untouched.

Removing the JBM service consists of deleting the messaging directory from the servers' deploy directory (restarting the servers after that).

Removing the JBM service from all of the other servers causes the NPE. Playing with the different deployments, the difference was whether the connection factories were deployed or not.

[gaohoward]

Hi,

Thanks. So the condition is:

1. starting a standalone JBM server node.
2. starting second node with messaging directory removed.
3. try connecting to the JBM server from the second node will cause NPE.

If my understand is correct, I think there is some thing you forget to remove in the second node. Do you have a test client for it?

[dejanb]

Thanks for your reply.

Yes,

This is exactly what happens. A standalone client connects OK both to the messaging server and to the second JBoss server accessing EJBs and MBeans.

Reading a previous JIRA issue (https://jira.jboss.org/jira/browse/JBMESSAGING-990) I think that some of the JBM aspects don't get deployed on the second server but I'm not sure how to test or force their deployment.

Regards,
Deyan