[jira] [Resolved] (AMQNET-483) MessageConsumer close when inside transaction is not idempotent.

["Timothy Bish (JIRA)" <ji...@apache.org>]

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

Timothy Bish resolved AMQNET-483.
---------------------------------

    Resolution: Fixed

Fixed on trunk and the 1.6.x fixes branch

> 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.0, 1.6.1, 1.6.2
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             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)