You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/07/09 09:08:04 UTC

[jira] [Resolved] (SLING-3736) Expose OSGi Installer state via JMX

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

Chetan Mehrotra resolved SLING-3736.
------------------------------------

       Resolution: Fixed
    Fix Version/s: Installer Core 3.5.4
         Assignee: Chetan Mehrotra

Applied the patch in http://svn.apache.org/r1609026

> Expose OSGi Installer state via JMX
> -----------------------------------
>
>                 Key: SLING-3736
>                 URL: https://issues.apache.org/jira/browse/SLING-3736
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: Installer Core 3.5.4
>
>         Attachments: SLING-3736.patch
>
>
>  Would be helpful to have OSGi installer expose an MBean which can provide information like
> * Current pending installations
> * Last OSGi installer state - Active, Suspended, Processed
> * Time of last activity
> This MBean can then be used by administrators to determine when its safe to shutdown Sling or start test say after installation of a patch.
> [1] http://markmail.org/thread/w235qqafagqvzlmm



--
This message was sent by Atlassian JIRA
(v6.2#6252)