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 2011/03/15 22:26:29 UTC

[jira] Closed: (AMQ-1722) Consumer not detectecting broker restart/stopping

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

Timothy Bish closed AMQ-1722.
-----------------------------

    Resolution: Not A Problem

Using the failover transport and having the inactivity monitor enabled will resolve this issue

> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira