You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2014/07/16 21:41:05 UTC
[jira] [Created] (AMQNET-483) MessageConsumer close when inside
transaction is not idempotent.
Timothy Bish created AMQNET-483:
-----------------------------------
Summary: MessageConsumer close when inside transaction is not idempotent.
Key: AMQNET-483
URL: https://issues.apache.org/jira/browse/AMQNET-483
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.6.2, 1.6.0, 1.6.1
Reporter: Timothy Bish
Assignee: Jim Gomes
Fix For: 1.6.3, 1.7.0
When a consumer is closed and it's session is transacted it registers a synchronization on the Session TransactionContext to complete the close after the transaction has been committed or rolled back. The synchronization can be added multiple times is close is called in succession but the synchronization doesn't check if the consumer has been closed when invoked so the transaction completion can result in several attempts to remove the same consumer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)