You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/10/08 12:48:40 UTC
[jira] Created: (AMQ-2966) Null messages occurring when using VM
transport, topics and multiple consumers
Null messages occurring when using VM transport, topics and multiple consumers
------------------------------------------------------------------------------
Key: AMQ-2966
URL: https://issues.apache.org/activemq/browse/AMQ-2966
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.4.1, 5.4.0
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.5.0
introduced by fix for https://issues.apache.org/activemq/browse/AMQ-2103
contention on marshaling message received over vm transport for the first time causes potential null. With multiple topic consumers there is contention as the message has not been unmarshalled on dispatch to the topic due to the vm transport being used.
moving the set to null out of the beforeMarahallMessage removes the potential sync window that causes the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2966) Null messages occurring when using VM
transport, topics and multiple consumers
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-2966.
-----------------------------
Resolution: Fixed
resolved in r1005773
> Null messages occurring when using VM transport, topics and multiple consumers
> ------------------------------------------------------------------------------
>
> Key: AMQ-2966
> URL: https://issues.apache.org/activemq/browse/AMQ-2966
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.0, 5.4.1
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.5.0
>
>
> introduced by fix for https://issues.apache.org/activemq/browse/AMQ-2103
> contention on marshaling message received over vm transport for the first time causes potential null. With multiple topic consumers there is contention as the message has not been unmarshalled on dispatch to the topic due to the vm transport being used.
> moving the set to null out of the beforeMarahallMessage removes the potential sync window that causes the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.