You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Ganesh (JIRA)" <ji...@apache.org> on 2015/06/15 22:06:00 UTC

[jira] [Commented] (AMQ-5844) Introduce logic into the failover transport not to recreate "aborted" slow consumers.

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

Ganesh commented on AMQ-5844:
-----------------------------

The FailoverTransport must remove slow consumer from its state so that the slow consumer is not re-registered if the connection falters. Please see attached patch and unit test

> Introduce logic into the failover transport not to recreate "aborted" slow consumers.
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-5844
>                 URL: https://issues.apache.org/jira/browse/AMQ-5844
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.11.1
>            Reporter: Ganesh
>            Priority: Minor
>
> AbortSlowConsumerStrategy can forcefully abort a slow consumer on the broker side if the consumer (client side) is not responding to the request to gracefully shutdown.
> If the connection between broker and consumer is subsequently lost, the failover transport recreates the connection and transparently re-registers all consumers on the broker side including those slow consumers that were previously forcefully aborted. 
> It would be good to introduce some logic into the failover transport to avoid recreating slow consumers that have already been "forcefully" aborted on broker. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)