[jira] [Commented] (AMQ-5794) Cleanup connections that open but don't initiate a protocol handshake.

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AMQ-5794:
------------------------------------------------------

Commit e5a94bfee2bc850f1999c58c2916655e8caba2d3 in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=e5a94bf ]

https://issues.apache.org/jira/browse/AMQ-5794 - duplex network case calls start twice and would start a connect check timer in error. Fix is to only start connectiontimeout if we have not already started the rest of the monitoring


> Cleanup connections that open but don't initiate a protocol handshake.
> ----------------------------------------------------------------------
>
>                 Key: AMQ-5794
>                 URL: https://issues.apache.org/jira/browse/AMQ-5794
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMS client, stomp, Transport
>    Affects Versions: 5.10.0, 5.10.1, 5.10.2, 5.11.0, 5.11.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.12.0
>
>
> The current inactivity monitor implementation only kicks in when the connection is opened an the protocol handshake completes such as when an OpenWire client sends its WireFormatInfo or when a STOMP client sends the CONNECT frame.
> We currently deal with this case for AMQP and MQTT by using a connection attempt timeout to close down connections that have opened but not started a handshake.  We should extend this to STOMP and OpenWire as well.  
> This issue has been seen in the STOMP over websockets where a STOMP WebSocket connection is opened but for some reason never initiates.  



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