felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niels Beekman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4728) InstanceManager concurrency issue
Date Fri, 19 Dec 2014 09:58:13 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253195#comment-14253195

Niels Beekman commented on FELIX-4728:

Thanks for the quick fix. Has a release date for 1.12.1 been set yet?

I think much of the InstanceManager code would benefit a lot from using modern synchronization
classes such as ConcurrentMap rather than a crude Collections.synchronizedMap(). I don't know
much about iPOJO internals, but this code path seems to be occurring for each and every dependency
access. Is there a limitation on JVM version that prevents iPOJO from being able to use these?

> InstanceManager concurrency issue
> ---------------------------------
>                 Key: FELIX-4728
>                 URL: https://issues.apache.org/jira/browse/FELIX-4728
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>    Affects Versions: ipojo-runtime-1.11.2
>            Reporter: Niels Beekman
>            Assignee: Clement Escoffier
>             Fix For: ipojo-runtime-1.12.1
> We observed a race condition in InstanceManager.onEntry. This is caused by improperly
synchronized access on a HashMap. Unlike reported in FELIX-3500, we did not get an exception,
but high cpu usage due to the data race. See the relevant thread stacks in the comments.

This message was sent by Atlassian JIRA

View raw message