[
https://issues.apache.org/activemq/browse/AMQ-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated AMQ-959:
-------------------------------
Fix Version/s: (was: 4.1.2)
4.1.1
> Wrong message removed from store when using composite destinations
> ------------------------------------------------------------------
>
> Key: AMQ-959
> URL: https://issues.apache.org/activemq/browse/AMQ-959
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.0.2
> Environment: AMQ4.0.2 using jdbc-persistence
> Reporter: Holger Bruch
> Fix For: 4.1.1, 4.2.0
>
> Attachments: CopyMessageId.diff
>
>
> When sending messages to composite destinations, for each simple destination
> a copy of the original message is created an sent. However, it's internal
> messageId is reused. As the messageId carries the brokerSequenceId, which is
> used as primary key in the jdbc message store, this is overwritten by the
> last send. All messages refer to the same store row so that the first
> acknowledge removes the content for all MessageReferences in memory.
> The attached patch creates a copy of the messageId when copying a message.
> Regards,
> Holger
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
