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

[David Lloyd (JIRA)]

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

David Lloyd commented on WFLY-9073:
-----------------------------------

I ask because (for example) ThreadPoolExecutor will create a new thread on every task submission up to the core size.  This means that if your pool size is (for example) 100, and your authentication attempt executes 10 tasks, it will cause 10 threads to be created; another similar attempt will create another 10 threads, etc.  So the observation of an increasing number of threads can be explained by defined behavior and is not actually a leak.  The state of the existent threads and the observation of a hang are all circumstantial bits of information.

> 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)