aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Siano (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARIES-1109) Duplicate subsystem ids after restart of subsystem.core
Date Mon, 02 Sep 2013 07:21:53 GMT

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

Stephan Siano updated ARIES-1109:
---------------------------------

    Attachment: c.esa
                b.esa
                a.esa
    
> Duplicate subsystem ids after restart of subsystem.core
> -------------------------------------------------------
>
>                 Key: ARIES-1109
>                 URL: https://issues.apache.org/jira/browse/ARIES-1109
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>            Reporter: Stephan Siano
>         Attachments: a.esa, b.esa, c.esa
>
>
> 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: http://www.atlassian.com/software/jira

Mime
View raw message