[
https://issues.apache.org/jira/browse/AMQ-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496569#comment-16496569
]
Christopher L. Shannon edited comment on AMQ-6981 at 5/31/18 1:50 PM:
----------------------------------------------------------------------
I forgot that when using the VM transport the message is supposed to be copied
on dispatch inside ActiveMQConnection so this may not be the exact issue, I
need to look at it a bit more.
was (Author: christopher.l.shannon):
I forgot that when using the VM transport the message is supposed to be copied
on dispatch isnide ActiveMQConnection so this may not be the exact issue, I
need to look at it a bit more.
> Concurrent access to ActiveMQTextMessage getText() can lead to 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
>
> Attachments: NullMessageTest.java
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
