4 Replies Latest reply on Jun 7, 2009 11:53 PM by Deyan Bektchiev

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

    Deyan Bektchiev Newbie

      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