activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Updated: (AMQ-1029) TransportConnector get duplicated when used with JMX
Date Mon, 26 Feb 2007 18:25:03 GMT


james strachan updated AMQ-1029:

    Fix Version/s:     (was: 4.1.2)

> TransportConnector get duplicated when used with JMX
> ----------------------------------------------------
>                 Key: AMQ-1029
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.0.2
>         Environment: Linux, ActiveMQ broker in a custom servlet, running on Tomcat 5.5.
>            Reporter: Andreas Mack
>            Priority: Minor
>             Fix For: 4.1.1, 4.2.0
>         Attachments: tc-jmx-patch
> The BrokerService keeps the configured TransportConnectors in a list called transportConnectors.
In startAllConnectors, the list is traversed and each connector is started through startTransportConnector().
This method checks if JMX is configured, and if so, it called connector.asManagedConnector()
which returns a new instance of a TransportConnector. This instance is started.
> But in the  transportConnectors list of BrokerService, the old, unstarted object is still
existent. Since a TransportConnector starts a TransportServiceDetector thread, the old, unstarted
instance contains a TSD that is not active. But the started TSD isn't referenced anymore.
> On shutdown, the old, unstarted TC and subsequently TSD are stopped. The "lost" instance
can't be touched anymore.
> My patch does this: During spin-up, startTransportConnector() returns the instance that
is started. The started instances are collected in an arraylist, this list replaces transportConnectors
after startup.
> Thanks to jstrachan for being patient on irc.

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

View raw message