[AMQ-6218] Message content returns null occasionally from Virtual Topic to the consumer

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.12.2, 5.13.2
• Fix Version/s: 5.13.3, 5.14.0
• External issue URL: http://activemq.2283324.n4.nabble.com/Message-content-returns-null-occasionally-from-Virtual-Topic-to-the-consumer-td4709151.html
• Assignee: Christopher L. Shannon
• Reporter: Rohit Sonawat
• Created: 17/Mar/16 12:33
• Updated: 14/Jun/16 14:37
• Resolved: 21/Mar/16 19:58

Description

I have 1 Virtual Topic and 40 Consumer to consume the messages sent by the topic. The problem is when I am sending thousands of Messages lets say 10000 via Virtual Topic I have noticed that 2 or 3 consumer are getting null as a text when I do message.getText(), but virtual topic is not sending a null as a text message if it so then all 40 consumer should report same.

I have also noticed this problem is not happening in AMQ v5.11 or with levelDB in AMQ v5.12.2/5.13.2. It is happening only in when you use kahaDB with AMQ v5.12.2/5.13.2

Issue Links

• is related to: AMQ-6256 ConcurentStoreAndDispatch can lead to inconsistent message states using VM Transport
• is related to: AMQ-6323 Support reduceMemoryFootprint flag for Topics
• relates to: AMQ-6221 ActiveMQTextMessage should synchronize on state changes