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

Posted to dev@activemq.apache.org by "Tom Coates (JIRA)" <ji...@apache.org> on 2010/10/06 00:08:41 UTC

[jira] Reopened: (AMQ-2553) Browsing DLQ over transacted session

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

Tom Coates reopened AMQ-2553:
-----------------------------


In 5.4.1 I'm seeing that browsing a queue in an XA transaction throws the exception previously commented.

> Browsing DLQ over transacted session
> ------------------------------------
>
>                 Key: AMQ-2553
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2553
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.3.1, 5.4.0
>
>
> When you browse DLQ over transacted session, a rollback is called when browser disconnects and can lead to messages to be sent to another DLQ (if their max redeliveries has been reached). The simple solution is to commit the session, just before destroying the consumer in those situations.

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