activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhi (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-6561) Broker does not close connection for all connection attempt errors
Date Mon, 16 Jan 2017 11:20:26 GMT

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

Abhi edited comment on AMQ-6561 at 1/16/17 11:19 AM:
-----------------------------------------------------

Hi Christopher,

I am looking to upgrade my ActiveMQ version (v5.11.1 to v5.14.x) and I just saw this bug.
Can this bug cause file descriptor leakage? When do you guys plan to release v5.14.4? Are
there any other bugs which i should wait for them to be fixed in 5.14.4? 


was (Author: xabhi):
Hi Christopher,

I am looking to upgrade my ActiveMQ version (v5.11.1 to v5.14.x) and I just saw to bug. When
do you guys plan to release v5.14.4? Are there any other bugs which i should wait for them
to be fixed in 5.14.4? 

> Broker does not close connection for all connection attempt errors
> ------------------------------------------------------------------
>
>                 Key: AMQ-6561
>                 URL: https://issues.apache.org/jira/browse/AMQ-6561
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.14.3
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.15.0, 5.14.4
>
>
> When a client connects to the broker the connection gets added inside the processAddConnection
method in TransportConnection.  Right now if there is an exception the socket is only shutdown
if the type of exception is SecurityException.  However the connection should really be closed
if any error occurs when trying to add the connection.  
> For example if an InvalidClientIDException occurs then the connection is no longer tracked
by the broker but the socket stays open until the client actually closes it on their end.
This should be fixed so that the error terminates the socket connection since the connection
attempt failed.



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

Mime
View raw message