[
https://issues.apache.org/jira/browse/AMQ-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693689#comment-14693689
]
Gary Tully commented on AMQ-5794:
---------------------------------
for the duplex network case - a workaround is to disable the connection timeout
check altogether on the broker that reuses the connection (ie: the one that
does not have a duplex=true networkConnector).
{code}<transportConnector name="openwire"
uri="tcp://0.0.0.0:61616?transport.connectAttemptTimeout=-1" />{code}
> 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)
