activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1420) limit non-ssl connection hangs up exceeding client(s)
Date Wed, 13 Sep 2017 15:37:00 GMT

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

ASF GitHub Bot commented on ARTEMIS-1420:
-----------------------------------------

Github user jbertram commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1534
  
    Can you elaborate on the use case where this is required?  The broker already has functionality
to close dead connections.  By implementing this feature you are hard-coding a 30 timeout
for *all* clients regardless of how they've configured their heart-beats.


> limit non-ssl connection hangs up exceeding client(s)
> -----------------------------------------------------
>
>                 Key: ARTEMIS-1420
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1420
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 2.3.0
>            Reporter: Stanislav Knot
>
> this is a max-negotiate-time. Maximum time a connection can take to send the initial
protocol negotiation, so time between creating tcp connection and sending the first frame.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message