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

[Piotr Krokowski (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-9073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434210#comment-13434210 ] 

Piotr Krokowski commented on WFLY-9073:
---------------------------------------

Forgive me, if my JVM knowledge is limited, but I'm not configuring any ThreadPoolExecutor, I'm not supplying any JVM parameters.
In this plain example, I'm running java with it's defaults, and observe, that the number of connections spikes, beyond any reasonable limit.
AFAIK the JMXConnectorFactory doesn't expose any API to inject any executor.
I'm also not aware of any global switches for JVM that would configure such limits (correct me if I'm wrong, I might learn something).

Please investigate the code, as I've highlighted in the description. The objects that are initialized during internalConnect are never cleaned up.

> 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
>            Assignee: Stuart Douglas
>         Attachments: JbossClientThreadLeakDemo.java
>
>
> 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.2.3#72005)