You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2017/04/10 11:42:41 UTC

[jira] [Commented] (AMQ-6647) Hanging threads when InvalidClientIDException occurs

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

Christopher L. Shannon commented on AMQ-6647:
---------------------------------------------

Which thread is not closed?  Do you have a stack trace?

Make sure you also test this on the newest version which is 5.14.4. There was a fix that might be related to this in 5.14.4 that has to do with sockets hanging open (and possibly a connection thread).  https://issues.apache.org/jira/browse/AMQ-6561

> Hanging threads when InvalidClientIDException occurs
> ----------------------------------------------------
>
>                 Key: AMQ-6647
>                 URL: https://issues.apache.org/jira/browse/AMQ-6647
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.10.0, 5.10.1, 5.11.0, 5.13.2
>            Reporter: Pavel Spatny
>            Priority: Minor
>
> We found an issue with hanging threads when connecting with the same clientID from multiple clients at the same time. The InvalidClientIDException occurs. It looks like there is incorrect EX handling and AMQ client can’t close some background thread.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)