[
https://issues.apache.org/jira/browse/AMQ-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon updated AMQ-6981:
----------------------------------------
Description:
The issue seems to involve using the VMTransport. 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.
was:
The issue occurs when using the VM transport to access the text of the
ActiveMQTextMsesage and the getText() method has to unmarshall data back into
text from the byte sequence.
The main problem is when there are multiple threads at the same time calling
getText() on the text message there is a race condition where the content can
be nulled out before finishing setting the text.
This is probably an issue with other message types besides a text message as
well.
> ActiveMQText message can return null when using VMTransport
> -----------------------------------------------------------
>
> Key: AMQ-6981
> URL: https://issues.apache.org/jira/browse/AMQ-6981
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker, JMS client
> Affects Versions: 5.15.4
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 5.16.0, 5.15.5
>
>
> The issue seems to involve using the VMTransport. 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
