[jboss-jira] [JBoss JIRA] (WFLY-9073) Thread Leak in jboss-client on JMX remoting authentication failure

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry reassigned WFLY-9073:
--------------------------------------

    Assignee:     (was: Stuart Douglas)


REMJMX-156 is the cloned issue. Since I believe Stuart was assigned to this just as the default assignee for "Application Client" component, that component isn't strongly involved, and I see no activity from him on this, I'm unassigning it. The real work would be on REMJMX-156.

> Thread Leak in jboss-client on JMX remoting authentication failure
> ------------------------------------------------------------------
>
>                 Key: WFLY-9073
>                 URL: https://issues.jboss.org/browse/WFLY-9073
>             Project: WildFly
>          Issue Type: Bug
>          Components: Application Client, JMX
>    Affects Versions: 10.1.0.Final
>            Reporter: Piotr Krokowski
>         Attachments: JbossClientThreadLeakDemo.java, close.png
>
>
> I've observed, that authentication failure, while connecting with jboss-client implementation of JMX remoting (remote+http) causes a thread leak. 
> Please find the attached code snippet to reproduce the faulty behavior.
> The attached code produces following output in my case :
> Thread count before starting:  2
> Active threads AFTER start: 2
> Connection failed.
> Active threads AFTER after success: 7
> Connection failed.
> Active threads AFTER after failure: 12
> Possible cause.
> After an initial analisys I've observed that RemotingConnector.internalConnect throws an Exception, while having state set to UNUSED, while I'd actually expect it being set to OPEN, as connection and endpoint fields are already initialized.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)