aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Siano (JIRA)" <>
Subject [jira] [Commented] (ARIES-1109) Duplicate subsystem ids after restart of subsystem.core
Date Fri, 30 Aug 2013 13:48:54 GMT


Stephan Siano commented on ARIES-1109:

I found this behaviour with the 1.0.0 release version (and the code you mentioned is in there).
Nevertheless this sets it to a wrong number (I even debugged it).

Funny thing is root.getDeploymentManifest().getHeaders().get("AriesSubsystem-LastId").getValue()
returned "4" in my last debug session (after I had installed several subsystems and restarted
the bundle some times) so this does seem to change sometimes. Unfortunately this is also wrong,
the largest installed subsystem id was 12 :-(
> Duplicate subsystem ids after restart of subsystem.core
> -------------------------------------------------------
>                 Key: ARIES-1109
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>            Reporter: Stephan Siano
> aries subsystems will generate duplicate subsystem ids if the subsystem core bundle (or
the container) is restarted.
> Reproduction is quite easy:
> 1. install a subsystem -> this will get subsystem id 1
> 2. stop the org.apache.aries.subsystem.core bundle (or the OSGi container)
> 3. start the org.apache.aries.subsystem.core bundle (or the OSGi container)
> -> the subsystem installed in step 1 is still there and has id 1
> 4. Install another subsystem (different from the first)
> -> This will also get Id 1
> I think the error is in line 150 of the org.apache.subsystems.core.internal.Subsystems
class. There the static lastId counter of the SubsystemIdentifier class is set to 0 before
actually populating the root subsystem.
> Maybe this should be set to the maximum id of the installed subsystems during or after
the population of the root subsystem

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message