When Testing JSR-286 Event, PortletContainerImpl.doEvent method throws 
NullPointer Exception
--------------------------------------------------------------------------------------------

                 Key: PLUTO-597
                 URL: https://issues.apache.org/jira/browse/PLUTO-597
             Project: Pluto
          Issue Type: Bug
          Components: portlet container
    Affects Versions: 2.0.0
         Environment: windows xp sp3 weblogic 11g
            Reporter: liazhang


Hello , everyone

I deployed pluto portal and testsuite on weblogic 11g. When testing Portlet 
Event,  for example click the Complex Payload Event Test or Simple Payload 
Event Test  very frequently, accasionally the container will throw the 
following Exception:
Exception in thread "testsuite.286TestPortlet!-1115531942|0" 
java.lang.NullPointerException
        at 
org.apache.pluto.driver.core.PortalRequestContext.getContext(PortalRequestContext.java:90)
        at 
org.apache.pluto.driver.services.container.PortletStateAwareResponseContextImpl.close(PortletStateAwareResponseContextImpl.java:69)
        at 
org.apache.pluto.container.impl.PortletContainerImpl.doEvent(PortletContainerImpl.java:423)
        at 
org.apache.pluto.driver.services.container.PortletWindowThread.run(PortletWindowThread.java:132),
and sometimes also companied with the following Exception:
Exception in thread "testsuite.286TestPortlet!-1115531942|0" 
java.lang.IllegalStateException: parameters map contains a values array which 
is empty or contains only null values
        at 
org.apache.pluto.container.impl.StateAwareResponseImpl.setRenderParameters(StateAwareResponseImpl.java:215)
        at 
org.apache.pluto.testsuite.TestPortlet.processStateAwarePhase(TestPortlet.java:173)
        at 
org.apache.pluto.testsuite.TestPortlet.processEvent(TestPortlet.java:178)
        at 
org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:140)
        at 
org.apache.pluto.testsuite.test.jsr286.filter.WildcardMappedFilter.doFilter(WildcardMappedFilter.java:66)
        at 
org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:129)
        at 
org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:71)
        at 
org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:91)
        at 
org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:368)
        at 
org.apache.pluto.container.driver.PortletServlet.doGet(PortletServlet.java:261)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at 
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
        at 
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
        at 
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
        at 
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
        at 
weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
        at 
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
        at 
org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233)
        at 
org.apache.pluto.driver.container.DefaultPortletInvokerService.event(DefaultPortletInvokerService.java:133)
        at 
org.apache.pluto.container.impl.PortletContainerImpl.doEvent(PortletContainerImpl.java:417)
        at 
org.apache.pluto.driver.services.container.PortletWindowThread.run(PortletWindowThread.java:132)

The exception does not occur every time, but it's easy to come out. You can 
click the  Complex Payload Event Test very quickly and can see the exceptions.

Does anybody know about the solution of this issue? 


-- 
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