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

[Yeray Borges (JIRA)]

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

Yeray Borges resolved WFLY-9073.
--------------------------------
    Fix Version/s: 11.0.0.Final
       Resolution: Done


The issue was solved in Wildfly 11.0.0.Final. In that version, the number of active threads reaches a maximum value and doesn't grow indefinitely.

> 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: JMX
>    Affects Versions: 10.1.0.Final
>            Reporter: Piotr Krokowski
>            Assignee: Yeray Borges
>             Fix For: 11.0.0.Final
>
>         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)