You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2018/05/31 13:42:00 UTC
[jira] [Updated] (AMQ-6981) Concurrent access to
ActiveMQTextMessage getText() can lead to null when using VMTransport
[ https://issues.apache.org/jira/browse/AMQ-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher L. Shannon updated AMQ-6981:
----------------------------------------
Attachment: NullMessageTest.java
> 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)