dangling thread after shutdown broker with a managed transport
--------------------------------------------------------------
Key: AMQ-1118
URL: https://issues.apache.org/activemq/browse/AMQ-1118
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.0.2, 4.0.1, 4.0
Environment: Windows XP, demand forwarding, failover == true
Reporter: Chris Hofstaedter
I ran into a problem in which I end up with an orphaned thread every time I
bounce a broker with a managed transport. I realize this may not be a big deal
in many scenarios, but we may end up bouncing our broker everytime a user
changes some configuration settings in our application and we need the app to
run indefinitely. So orphaned threads are a concern to me.
I traced it down to BrokerService.startTransportConnector().
In this function, if isUseJmx() returns true, the connector is
decorated/replaced through a call to connector.asManagedConnector(). Turns out
the broker never stores the reference to the newly created managed connector
anywhere. I added transportConnectors.add(connector)
to add the new managed connector to the broker's container of connectors and it
seems to work in that all threads are shutdown cleanly even when the transport
connector is managed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
