activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carel-Andre Gåsemyr (JIRA) <j...@apache.org>
Subject [jira] Commented: (AMQ-1722) Consumer not detectecting broker restart/stopping
Date Thu, 12 Jun 2008 11:44:00 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43434#action_43434
] 

Carel-Andre Gåsemyr commented on AMQ-1722:
------------------------------------------

Not sure if AMQ-1645 have something to do with this issue, but the workaround for this seems
to be using failover transport.



> Consumer not detectecting  broker restart/stopping
> --------------------------------------------------
>
>                 Key: AMQ-1722
>                 URL: https://issues.apache.org/activemq/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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message