You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2008/10/29 14:37:52 UTC

[jira] Created: (AMQ-1989) STOMP - transaction header is not removed from messages received in a transaction

STOMP - transaction header is not removed from messages received in a transaction
---------------------------------------------------------------------------------

                 Key: AMQ-1989
                 URL: https://issues.apache.org/activemq/browse/AMQ-1989
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.2.0
            Reporter: Dejan Bosanac
            Assignee: Dejan Bosanac
            Priority: Minor
             Fix For: 5.3.0


There is no need to keep this information in a message. This can make a problem if client tries to ack a message from other transaction (and just copy all headers from the message).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (AMQ-1989) STOMP - transaction header is not removed from messages received in a transaction

Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/activemq/browse/AMQ-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac resolved AMQ-1989.
--------------------------------

    Resolution: Fixed

Fixed in SVN revision 726668

> STOMP - transaction header is not removed from messages received in a transaction
> ---------------------------------------------------------------------------------
>
>                 Key: AMQ-1989
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1989
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>            Priority: Minor
>             Fix For: 5.3.0
>
>
> There is no need to keep this information in a message. This can make a problem if client tries to ack a message from other transaction (and just copy all headers from the message).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.