activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-2775) Race condition in org.apache.activemq.util.osgi.Activator
Date Sat, 02 Nov 2013 21:01:17 GMT

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

Claus Ibsen updated AMQ-2775:
-----------------------------

      Component/s: OSGi/Karaf
         Priority: Minor  (was: Major)
    Fix Version/s:     (was: 5.x)
                   5.10.0
       Issue Type: Improvement  (was: Bug)

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

Mime
View raw message