[
https://issues.apache.org/jira/browse/AMQ-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511439#comment-13511439
]
Timothy Bish commented on AMQ-4207:
-----------------------------------
I'm guessing here that you have one thread that's calling the rollback and
another that's calling the close of the Session.
> NullPointerException in ActiveMQSession.rollback()
> --------------------------------------------------
>
> Key: AMQ-4207
> URL: https://issues.apache.org/jira/browse/AMQ-4207
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.5.1, 5.6.0, 5.7.0
> Reporter: Vadim Pesochinskiy
> Priority: Minor
> Fix For: 5.x
>
>
> Sometimes we get this exception:
> java.lang.NullPointerException
> at org.apache.activemq.ActiveMQSession.rollback(ActiveMQSession.java:581)
> at
> com.barra.cp.common.activemq.MultiQueueReceiver.rollback(MultiQueueReceiver.java:212)
> at
> com.barra.cp.common.activemq.MultiQueueReceiver.onMessage(MultiQueueReceiver.java:185)
> The synchronized dispose() method nulls the transactionContext and sets
> closed to true. In many places in the code, not synchronized code checks
> closed member variable and later references transactionContext, which can
> become null by that time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
