You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/08/27 21:20:07 UTC
[jira] [Commented] (SLING-2581) ConfigAdmin MBean does not come
back up when changing run level to <10 and back up
[ https://issues.apache.org/jira/browse/SLING-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442637#comment-13442637 ]
Felix Meschberger commented on SLING-2581:
------------------------------------------
This is a known issue and has been fixed (I don't know the Aries issue right now).
> ConfigAdmin MBean does not come back up when changing run level to <10 and back up
> ----------------------------------------------------------------------------------
>
> Key: SLING-2581
> URL: https://issues.apache.org/jira/browse/SLING-2581
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Affects Versions: Launchpad Builder 6
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> To reproduce:
> -Start launchpad jar
> -The osgi.compendium:service=cm JMX MBean is available
> -Change to run level 9 (which stops ConfigAdmin)
> -MBean correctly disappears
> -Change back to run level 20, ConfigAdmin is available again
> -MBean does not come back
> That's probably an issue in the Aries JMX bundles that we're using - for now I'm just reporting this so that we have a trace, not planning to work on it right now
--
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