geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Viet Hung Nguyen (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-3996) Clicking "Test these settings" leads to 500 error in admin console
Date Fri, 16 May 2008 01:04:55 GMT

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

Viet Hung Nguyen closed GERONIMO-3996.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1
                   2.2

Committed revision 656911 in branches/2.1

> Clicking "Test these settings" leads to 500 error in admin console
> ------------------------------------------------------------------
>
>                 Key: GERONIMO-3996
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3996
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, monitoring
>    Affects Versions: 2.1
>         Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3
> HW: intel x86 32bit
>            Reporter: Xia Ming
>            Assignee: Viet Hung Nguyen
>            Priority: Minor
>             Fix For: 2.2, 2.1
>
>
> When monitoring a remote Geronimo server, if the remote server is shutdown, then click
"Test these settings" of that remote server monitoring in the Edit page, the 500 error will
be shown. The specific exception as below:
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling
this request.
> exception
> java.lang.IllegalArgumentException: Render parameter key or value must not be null.
> 	org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179)
> 	org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234)
> 	org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218)
> 	org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> 	org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
> 	org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85)
> 	org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219)
> 	org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112)
> 	org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot
logs.
> Apache Tomcat/6.0-snapshot

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


Mime
View raw message