activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQCPP-501) Consumers remain active after being deleted
Date Thu, 18 Jul 2013 14:18:48 GMT

    [ https://issues.apache.org/jira/browse/AMQCPP-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712364#comment-13712364
] 

Timothy Bish commented on AMQCPP-501:
-------------------------------------

The fix is definitely not valid as it bypasses the transaction checks of the close method.
 I'm guessing that your session is transacted?  You should provide a complete unit test, can't
really do much with the snippet.  
                
> Consumers remain active after being deleted
> -------------------------------------------
>
>                 Key: AMQCPP-501
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-501
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>            Reporter: Andrei Gheorghe
>            Assignee: Timothy Bish
>            Priority: Trivial
>         Attachments: ActiveMQConsumer.cpp.patch, test code.txt
>
>
> I'm not really sure if this is a problem or not. Deleting a consumer doesn't free all
his prefetched messsages so they can't be consumed by another consumer and the number of consumers
remains the same in the web interface. Calling close before deleting them solves the problem
but I was expecting the destructor cu cleanup after itself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message