Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Tue, 27 Mar 2012 03:17:44 +0000 (UTC)
From: "xiezhi (Updated) (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: 
 <128823837.21555.1332818264210.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2120378335.1742.1314775270442.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (GERONIMO-6135) Status changed abnormal for
 default server in mornitoring on admin console
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

xiezhi updated GERONIMO-6135:
-----------------------------

    Attachment: monitoringNormal.jsp.patch

I have done some modification.
                
> Status changed abnormal for default server in mornitoring on admin console
> --------------------------------------------------------------------------
>
>                 Key: GERONIMO-6135
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6135
>             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: xiezhi
>            Priority: Minor
>             Fix For: 3.0, 3.0-beta-2
>
>         Attachments: monitoringNormal.jsp.patch, monitoringStatus.patch
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira