activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Demian Mrakovich (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2553) Browsing DLQ over transacted session
Date Thu, 20 May 2010 15:56:24 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59476#action_59476
] 

Demian Mrakovich commented on AMQ-2553:
---------------------------------------

This causes an exception on regular queues if in a XA transaction.

 javax.jms.TransactionInProgressException: Cannot commit() if an XA transaction is already
in progress 
2010-05-20 17:22:21,453 ERROR [STDERR] (WorkManager(2)-13)      at org.apache.activemq.TransactionContext.commit(TransactionContext.java:277)
2010-05-20 17:22:21,453 ERROR [STDERR] (WorkManager(2)-13)      at org.apache.activemq.ra.ManagedTransactionContext.commit(ManagedTransactionContext.java:62)
2010-05-20 17:22:21,454 ERROR [STDERR] (WorkManager(2)-13)      at org.apache.activemq.ActiveMQSession.commit(ActiveMQSession.java:558)
2010-05-20 17:22:21,454 ERROR [STDERR] (WorkManager(2)-13)      at org.apache.activemq.ActiveMQQueueBrowser.destroyConsumer(ActiveMQQueueBrowser.java:117)
2010-05-20 17:22:21,454 ERROR [STDERR] (WorkManager(2)-13)      at org.apache.activemq.ActiveMQQueueBrowser.close(ActiveMQQueueBrowser.java:206)


> 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.


Mime
View raw message