[
https://issues.apache.org/jira/browse/AMQ-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812170#comment-13812170
]
Claus Ibsen commented on AMQ-2775:
----------------------------------
I think this is a general problem for all osgi activators, and not really a bug
per see. But we could maybe make the methods synchronized.
> Race condition in org.apache.activemq.util.osgi.Activator
> ---------------------------------------------------------
>
> Key: AMQ-2775
> URL: https://issues.apache.org/jira/browse/AMQ-2775
> Project: ActiveMQ
> Issue Type: Improvement
> Components: OSGi/Karaf
> Affects Versions: 5.3.2
> Reporter: Michael Pilquist
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 5.10.0
>
>
> There's a race condition between start and create methods of Activator. If a
> bundle that was started before activemq-core does something that causes a
> call to Activator.create, and Activator.start is still scanning bundles for
> contributed service files, an IOException results.
> In practice, this occurred after upgrading from 5.3.0 to 5.3.2 because
> another bundle at the same start level as activemq-core programmatically
> instantiated a broker from a different thread. The activemq-core activator
> was still scanning the installed bundles and hadn't gotten to itself yet, so
> the result was a failure to instantiate the tcp handler.
> Making start/create/stop synchronized would fix this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
