You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Shawn Jiang (JIRA)" <ji...@apache.org> on 2008/12/31 08:40:46 UTC

[jira] Created: (GERONIMO-4487) Can't disable/enable a server in monitoring portlet.

Can't disable/enable a server in monitoring portlet.
----------------------------------------------------

                 Key: GERONIMO-4487
                 URL: https://issues.apache.org/jira/browse/GERONIMO-4487
             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


# 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 and 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.


[jira] Closed: (GERONIMO-4487) Can't disable/enable a server in monitoring portlet.

Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods closed GERONIMO-4487.
----------------------------------


Fix verified by Shawn.  Moving to Closed state.

> Can't disable/enable a server in monitoring portlet.
> ----------------------------------------------------
>
>                 Key: GERONIMO-4487
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4487
>             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: Donald Woods
>             Fix For: 2.2
>
>         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.


[jira] Updated: (GERONIMO-4487) Can't disable/enable a server in monitoring portlet.

Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods updated GERONIMO-4487:
-----------------------------------

       Regression: [Regression]
    Fix Version/s: 2.2
         Assignee: Donald Woods  (was: Shawn Jiang)

> Can't disable/enable a server in monitoring portlet.
> ----------------------------------------------------
>
>                 Key: GERONIMO-4487
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4487
>             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: Donald Woods
>             Fix For: 2.2
>
>         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.


[jira] Updated: (GERONIMO-4487) Can't disable/enable a server in monitoring portlet.

Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn Jiang updated GERONIMO-4487:
----------------------------------

    Attachment: G4487_Shawn.patch

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

There's another un-defined "graphById" @NamedQuery of Graph.java 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: https://issues.apache.org/jira/browse/GERONIMO-4487
>             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.


[jira] Updated: (GERONIMO-4487) Can't disable/enable a server in monitoring portlet.

Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn Jiang updated GERONIMO-4487:
----------------------------------


Patch for this defect is available, please help review it.  Thanks.

> Can't disable/enable a server in monitoring portlet.
> ----------------------------------------------------
>
>                 Key: GERONIMO-4487
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4487
>             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.


[jira] Resolved: (GERONIMO-4487) Can't disable/enable a server in monitoring portlet.

Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods resolved GERONIMO-4487.
------------------------------------

    Resolution: Fixed

Committed patch from Shawn to trunk (2.2-SNAPSHOT) as Rev731939.

> Can't disable/enable a server in monitoring portlet.
> ----------------------------------------------------
>
>                 Key: GERONIMO-4487
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4487
>             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: Donald Woods
>             Fix For: 2.2
>
>         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.


[jira] Updated: (GERONIMO-4487) Can't disable/enable a server in monitoring portlet.

Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn Jiang updated GERONIMO-4487:
----------------------------------

    Description: 
# 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."

  was:
# 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 and RED error on screen.  "[ERROR] Server with server_id=xxx  could not be disabled/enabled."


> Can't disable/enable a server in monitoring portlet.
> ----------------------------------------------------
>
>                 Key: GERONIMO-4487
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4487
>             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
>
> # 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.


[jira] Commented: (GERONIMO-4487) Can't disable/enable a server in monitoring portlet.

Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662227#action_12662227 ] 

Shawn Jiang commented on GERONIMO-4487:
---------------------------------------

I've verified that this is fixed in the latest trunk snapshot build, thanks.

> Can't disable/enable a server in monitoring portlet.
> ----------------------------------------------------
>
>                 Key: GERONIMO-4487
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4487
>             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: Donald Woods
>             Fix For: 2.2
>
>         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.