geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "xiezhi (Commented) (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6135) Status changed abnormal for default server in mornitoring on admin console
Date Wed, 07 Mar 2012 07:31:57 GMT


xiezhi commented on GERONIMO-6135:

Investigated this jira. Found after clicked the "Disable Query", the server will stop SnopshotThread
and set threadstatus=-1. Then the page reload and checked the snapshot status. At this time
the thread is still stopping and the status is still -1. So it show "Stopping". When you refresh
this page, the thread stopped. So the page show "Stat.Query" status is "Stopped". Because
the page just refresh once after click the link. So the status is still be stopping even if
the thread has stopped.
> Status changed abnormal for default server in mornitoring on admin console
> --------------------------------------------------------------------------
>                 Key: GERONIMO-6135
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: monitoring
>    Affects Versions: 3.0
>         Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623
(JIT enabled, AOT enabled)
>            Reporter: Tina Li
>            Assignee: Shenghao Fang
>            Priority: Minor
> 1. Use the Aug 23's build of geronimo-3.0 snapshot
> 2. Go to the "Monitoring" porlet on admin console
> 3. Click the 'Enable Query' link associated with this default server, server works well
> 4. Click the "Disable Query" link but found the value of "Stat.Query" for the default
server keeps "Stopping..." ,Not changed to "Stopped" until you refreshed this page.

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


View raw message