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
    Affects Versions: 2.1
         Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3
HW: intel x86 32bit
            Reporter: Xia Ming
            Priority: Minor


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.

Reply via email to