You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2011/03/04 22:45:46 UTC

[jira] Created: (UIMA-2084) Extend UIMA AS service JMX API to dump service state

Extend UIMA AS service JMX API to dump service state
----------------------------------------------------

                 Key: UIMA-2084
                 URL: https://issues.apache.org/jira/browse/UIMA-2084
             Project: UIMA
          Issue Type: Improvement
          Components: Async Scaleout
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
            Priority: Minor
             Fix For: 2.3.1AS


Currently UIMA AS jmx service InfoMBean shows the state of a service as INITIALIZING, RUNNING, DISABLED, STOPPING, or FAILED. Extend UIMA AS aggregate to show the state of each delegate both remote and co-located. In case the aggregate is hung during initialization, dumping state of each delegate may help pin point a cause of the hang if the culprit is a delegate. When a delegate returns its metadata to the aggregate its state should change from INITIALIZING to RUNNING.  

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (UIMA-2084) Extend UIMA AS service JMX API to dump service state

Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-2084:
--------------------------------

    Description: Currently UIMA AS jmx service InfoMBean shows the state of a service as INITIALIZING, RUNNING, DISABLED, STOPPING, or FAILED. Extend UIMA AS aggregate to show the state of each delegate both remote and co-located. In case the aggregate is hung during initialization, dumping state of each delegate may help pin point a cause of the hang if the culprit is a delegate. When a delegate returns its metadata to the aggregate its state should change from INITIALIZING to RUNNING. Modify service JMX InfoMBean to include a new method dumpState() to enable dumping state of each UIMA AS service.    (was: Currently UIMA AS jmx service InfoMBean shows the state of a service as INITIALIZING, RUNNING, DISABLED, STOPPING, or FAILED. Extend UIMA AS aggregate to show the state of each delegate both remote and co-located. In case the aggregate is hung during initialization, dumping state of each delegate may help pin point a cause of the hang if the culprit is a delegate. When a delegate returns its metadata to the aggregate its state should change from INITIALIZING to RUNNING.  )

> Extend UIMA AS service JMX API to dump service state
> ----------------------------------------------------
>
>                 Key: UIMA-2084
>                 URL: https://issues.apache.org/jira/browse/UIMA-2084
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>             Fix For: 2.3.1AS
>
>
> Currently UIMA AS jmx service InfoMBean shows the state of a service as INITIALIZING, RUNNING, DISABLED, STOPPING, or FAILED. Extend UIMA AS aggregate to show the state of each delegate both remote and co-located. In case the aggregate is hung during initialization, dumping state of each delegate may help pin point a cause of the hang if the culprit is a delegate. When a delegate returns its metadata to the aggregate its state should change from INITIALIZING to RUNNING. Modify service JMX InfoMBean to include a new method dumpState() to enable dumping state of each UIMA AS service.  

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (UIMA-2084) Extend UIMA AS service JMX API to dump service state

Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-2084.
-------------------------------

    Resolution: Fixed

Added new API to UIMA AS ServiceInfo MBean to enable dumping of service state. The new method dumpState() is now available in the MBean Operations. UIMA AS Aggregate traverses all its delegates asking each to dump state. If the delegate is a co-located Aggregate, its delegates are asked to dump state. This produces a complete state of all internal components. The state of a delegate is changed to RUNNING if it responds to GetMeta to its client.  

> Extend UIMA AS service JMX API to dump service state
> ----------------------------------------------------
>
>                 Key: UIMA-2084
>                 URL: https://issues.apache.org/jira/browse/UIMA-2084
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>             Fix For: 2.3.1AS
>
>
> Currently UIMA AS jmx service InfoMBean shows the state of a service as INITIALIZING, RUNNING, DISABLED, STOPPING, or FAILED. Extend UIMA AS aggregate to show the state of each delegate both remote and co-located. In case the aggregate is hung during initialization, dumping state of each delegate may help pin point a cause of the hang if the culprit is a delegate. When a delegate returns its metadata to the aggregate its state should change from INITIALIZING to RUNNING. Modify service JMX InfoMBean to include a new method dumpState() to enable dumping state of each UIMA AS service.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira