You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Ronny H. Ringen (JIRA)" <ji...@apache.org> on 2013/02/25 15:16:13 UTC
[jira] [Commented] (AMQ-1722) Consumer not detectecting broker
restart/stopping
[ https://issues.apache.org/jira/browse/AMQ-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585873#comment-13585873 ]
Ronny H. Ringen commented on AMQ-1722:
--------------------------------------
Did using the inactivity monitor resolve the issue? I have the same problem (on amq 5.6.0 (broker is 5.5.1)) and adding the inactivity monitor had noe effect.
> Consumer not detectecting broker restart/stopping
> --------------------------------------------------
>
> Key: AMQ-1722
> URL: https://issues.apache.org/jira/browse/AMQ-1722
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.1.0
> Environment: Windows XP, eclipse 3.2
> Reporter: Carel-Andre GĂ„semyr
> Fix For: NEEDS_REVIEWED
>
>
> I have a test to assure a message consumer is still consuming messages after a central broker restart, using org.springframework.jms.listener.DefaultMessageListenerContainer.
> The channel never detects the broker shutting down.
> org.apache.activemq.MessageDispatchChannel.isClosed() returns "false" when org.apache.activemq.ActiveMQMessageConsumer is validating the connection.
> I found org.apache.activemq.MessageDispatchChannel.close() is newer called when the broker is stopped. This was working in 5.0.0
--
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