[AMQ-6981] ActiveMQText message can return null when using VMTransport

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.15.4
• Component/s: Broker, JMS client
• Assignee: Unassigned
• Reporter: Christopher L. Shannon
• Created: 31/May/18 13:38
• Updated: 31/May/18 20:04

Description

The issue seems to involve using the VMTransport, however it's possible it could be something else because the NIO transport is also used in the test case.

The original bug report is here:

http://mail-archives.apache.org/mod_mbox/activemq-dev/201805.mbox/%3C1527716475007-0.post%40n4.nabble.com%3E

Test Report is here:

https://github.com/CodeMettle/amq_null_body_repro

Originally I thought this had to do with concurrently accessing getText() on a message but the VM transport should copy the message to each consumer before dispatch so something else seems to be going on.

It's possible that there's something specific to the test case (ie a bug in the client code) or an issue in the broker that causes the null message body but this needs to be looked at closer to determine the problem.

Also, as a side note, there is no specific synchronization in the client message objects as they are supposed to be used in a single thread which is why they are copied on dispatch if using the VM transport.