[
https://issues.apache.org/jira/browse/ARTEMIS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397180#comment-15397180
]
ASF GitHub Bot commented on ARTEMIS-642:
----------------------------------------
Github user bayern39 commented on the issue:
https://github.com/apache/activemq-artemis/pull/672
@clebertsuconic Hi,Clebert,I have committed a new,I have done as you say,
add a check of version ID and don't store the sessionContexts,but the last you
sayed "rough the ProtocolManagers somehow",I try to do it,but it maybe
inconvenient and difficult, so in order to not do a protocol specific
implementation on QueueImpl,I have add a new method in the Interface of
RemotingConnection,this is my solution,what do you think about it?
> Disable slow client reconnecting with KILL slow client policy
> -------------------------------------------------------------
>
> Key: ARTEMIS-642
> URL: https://issues.apache.org/jira/browse/ARTEMIS-642
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 1.3.0
> Reporter: Chen Maoqian
> Priority: Minor
>
> It is possible to detect and handle(KILL, NOTIFY) slow consumers. In case
> policy KILL is used and connection factory used to create connection of slow
> consumer has attribute reconnect-attempts set to "-1", slow consumer
> reconnects to server. This consumer is then reconnects, is detected as slow
> and disconnected.
> Attribute reconnect-attempts="-1" should be ignored, and slow client should
> not be trying to reconnect once it is disconnected by KILL slow consumer
> policy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
