JMS Error

[Shaji Markose]

Hi 

Our XNAT version 1.9.3.1, build 208 with container-service-3.7.2-fat.jar sent JMS error as follows. Application is up running, but seems like a problem in handling null pointer exception.

Thanks

Shaji

class org.springframework.jms.listener.adapter.ListenerExecutionFailedException Listener method 'public void org.nrg.containers.events.listeners.ContainerServiceWorkflowStatusEventListener.onRequest(org.nrg.xft.event.entities.WorkflowStatusEvent)' threw exception; nested exception is java.lang.NullPointerException

org.springframework.jms.listener.adapter.ListenerExecutionFailedException: Listener method 'public void org.nrg.containers.events.listeners.ContainerServiceWorkflowStatusEventListener.onRequest(org.nrg.xft.event.entities.WorkflowStatusEvent)' threw exception; nested exception is java.lang.NullPointerException        at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.invokeHandler(MessagingMessageListenerAdapter.java:118)        at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.onMessage(MessagingMessageListenerAdapter.java:84)        at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:736)        at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:696)        at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:674)        at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:331)        at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:270)        at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1237)        at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1127)        at java.lang.Thread.run(Thread.java:750)Caused by: java.lang.NullPointerException        at org.nrg.containers.events.model.SessionMergeOrArchiveEvent.create(SessionMergeOrArchiveEvent.java:29)        at org.nrg.containers.events.listeners.ContainerServiceWorkflowStatusEventListener.processSessionWorkflowEvent(ContainerServiceWorkflowStatusEventListener.java:103)        at org.nrg.containers.events.listeners.ContainerServiceWorkflowStatusEventListener.onRequest(ContainerServiceWorkflowStatusEventListener.java:92)        at sun.reflect.GeneratedMethodAccessor1031.invoke(Unknown Source)        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)        at java.lang.reflect.Method.invoke(Method.java:498)        at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:169)        at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:119)        at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.invokeHandler(MessagingMessageListenerAdapter.java:110)

[Rick Herrick]

Hey Shaji,

We're not sure about the root cause of this issue. Basically in some cases the session passed into the JMS listener is null (i.e. it doesn't exist, which doesn't really make sense since it was just merged or archived), but in that cade the code shouldn't explode like this. We added a fix to detect the null session and log some info about the initial event to try and understand why this is happening. That fix will be in one of the upcoming container service releases, either 3.7.4 or 3.8.0.

Rick Herrick 

Senior Software Developer

ri...@xnatworks.io

https://xnatworks.io | Find us on LinkedIn! 

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/ce43811d-0a39-4941-96aa-f61bd3ee74b2n%40googlegroups.com.