geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Jiang (JIRA)" <>
Subject [jira] Updated: (GERONIMO-4487) Can't disable/enable a server in monitoring portlet.
Date Wed, 31 Dec 2008 07:52:44 GMT


Shawn Jiang updated GERONIMO-4487:

    Attachment: G4487_Shawn.patch

The problem is caused by a un-defined "nodeByName" @NamedQuery  of being called
by MonitoringPortlet.alterServerState();  This patch added the @NamedQuery "nodeByName" in to fix this defect.   

There's another un-defined "graphById" @NamedQuery of was called.  which will cause
a exception when user click the graph id to see the graph in a poped up graph in monitoringPopUpGraph.jsp.
 This patch also addressed this problem.

> Can't disable/enable a server in monitoring portlet.
> ----------------------------------------------------
>                 Key: GERONIMO-4487
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: monitoring
>    Affects Versions: 2.2
>         Environment: windows XP, sun JDK 1.5
>            Reporter: Shawn Jiang
>            Assignee: Shawn Jiang
>         Attachments: G4487_Shawn.patch
> # create a server in monitoring portlet.
> # click servers->actions->disable/enable to disable/enable the server.
> * *expected result:* the server could be disabled/enabled without any problems.
> * *actual result:* the server can's be disabled/enabled with a RED error on screen. 
"[ERROR] Server with server_id=xxx  could not be disabled/enabled."

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message