[jira] Assigned: (AMQ-1483) unsuccessful NetworkConnector connections leak threads

["Rob Davies (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies reassigned AMQ-1483:
-------------------------------

    Assignee: Rob Davies

> unsuccessful NetworkConnector connections leak threads
> ------------------------------------------------------
>
>                 Key: AMQ-1483
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1483
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 4.1.1
>            Reporter: Norbert Kiesel
>            Assignee: Rob Davies
>
> I have a pair of (embedded) brokers connected via a NetworkConnector:
>     <networkConnectors>
>       <networkConnector name="secondary" uri="static://(ssl://192.168.4.3:4081)" networkTTL="5" prefetchSize="1"/>
>     </networkConnectors>
> When the receiving broker is not running, the sender tries to reconnect every 5 seconds.  While doing that, it leaks threads (seems like about 2 threads per minute). Checking with jconsole, all hanging threads are doing:
> Name: JMX server connection timeout 85
> State: TIMED_WAITING on [I@38f04c
> Total blocked: 0  Total waited: 143
> Stack trace: 
> java.lang.Object.wait(Native Method)
> com.sun.jmx.remote.internal.ServerCommunicatorAdmin$Timeout.run(ServerCommunicatorAdmin.java:150)
> java.lang.Thread.run(Thread.java:595)
> The threads that are created every 5 seconds look like this in jconsole:
> Name: Thread-2060
> State: TIMED_WAITING on java.lang.Object@a06577
> Total blocked: 0  Total waited: 1
> Stack trace: 
> java.lang.Object.wait(Native Method)
> org.apache.activemq.transport.discovery.simple.SimpleDiscoveryAgent$1.run(SimpleDiscoveryAgent.java:139)
> If that issue is fixed in 5.0: can someone please tell me if/how that fix can be backported to 4.1.1?
> Best,
>   Norbert

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.