You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Holger Bruch (JIRA)" <ji...@apache.org> on 2006/10/06 20:16:09 UTC

[jira] Created: (AMQ-959) Wrong message removed from store when using composite destinations

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
         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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (AMQ-959) Wrong message removed from store when using composite destinations

Posted by "Jonas Lim (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-959?page=all ]

Jonas Lim resolved AMQ-959.
---------------------------

    Fix Version/s: 4.1.2
                   4.2.0
       Resolution: Fixed

Thanks! 

patch applied in :
trunk : 477171
4.1 branch : 477173

> 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.2, 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira