[jira] [Comment Edited] (AMQ-8031) ActiveMQ classic - OpenWire transport connector (nio+ssl) does not actively close silent connections

["Martin Lichtin (Jira)" <ji...@apache.org>]

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

Martin Lichtin edited comment on AMQ-8031 at 9/2/20, 5:03 PM:
--------------------------------------------------------------

Will try, but I doubt it. the socket timeout seems used only to set the timeout for how long to stay in the accept() call, I believe.

It is in addition used on the client side during an SSL handshake, but that's another situation.


was (Author: lichtin):
Will try, but I doubt it. the socket timeout seems used only to set the timeout for how long to stay in the accept() call, I believe.

It is in addition used during an SSL handshake, but that's another situation.

> ActiveMQ classic - OpenWire transport connector (nio+ssl) does not actively close silent connections
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-8031
>                 URL: https://issues.apache.org/jira/browse/AMQ-8031
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Martin Lichtin
>            Priority: Major
>
> ActiveMQ classic - OpenWire transport connector (nio+ssl) does not actively close silent connections.
> This can be reproduced with an SSL enabled Activemq broker, e.g.
> {{<transportConnector name="openwire-ssl" uri="nio+ssl://AMQ-IP:AMQ-PORT?maximumConnections=100" />}}
> Simply opening dummy connections towards this server by using
> {{for i in $(seq 200); do echo $i; ncat --recv-only AMQ-IP AMQ-PORT & done}}
> will cause the server to eventually run out of connections.
> I'd expect "silent" connections to be dropped pretty quickly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)