[AMQ-5426] ActiveMQMessageConsumer could run into NPE due to concurrent access to internal state

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.8.0, 5.9.1, 5.10.0
• Fix Version/s: 5.13.4, 5.14.0
• Component/s: JMS client
• Assignee: Christopher L. Shannon
• Reporter: Michael Wong
• Created: 07/Nov/14 01:13
• Updated: 06/Jul/16 15:08
• Resolved: 05/Jul/16 20:11

Description

ActiveMQMessageConsumer could run into NPE when the consumer is closing and a message arrived at the same time.

Here is the stacktrace:
java.lang.NullPointerException
at org.apache.activemq.ActiveMQMessageConsumer.ackLater(ActiveMQMessageConsumer.java:979)
at org.apache.activemq.ActiveMQMessageConsumer.afterMessageIsConsumed(ActiveMQMessageConsumer.java:929)
at org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1323)
at org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
at org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Issue Links

• is duplicated by: AMQ-5425 ActiveMQMessageConsumer race condition