[gatein-issues] [JBoss JIRA] (GTNPORTAL-2917) NPEs thrown while accessing /portal context when JPP is being started

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/GTNPORTAL-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766423#comment-12766423 ] 

RH Bugzilla Integration commented on GTNPORTAL-2917:
----------------------------------------------------

theute at redhat.com made a comment on [bug 948301|https://bugzilla.redhat.com/show_bug.cgi?id=948301]

Unfortunately, it's a known issue due to the fact that JBossWeb in AS7 (unlike AS5) starts to accept incoming request before it's fully started.

We've already looked for a solution, but AFAIK there is none (unless JPP is not directly facing the requests).

We can keep the bug open for the records though as I don't think it was ever filled-in.
                
> NPEs thrown while accessing /portal context when JPP is being started
> ---------------------------------------------------------------------
>
>                 Key: GTNPORTAL-2917
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2917
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.5.0.Final, 3.6.0.Beta01
>            Reporter: Dominik Pospisil
>              Labels: JPP61-Test-dev
>             Fix For: 3.6.0.Final
>
>
> JPP throws NPE if a client tries to access /portal context during server startup. The NPEs occur after the server logs "Registering web context: /portal" until the portal EAR is competely deployed.
> Steps to Reproduce:
> 1. start the server
> 2. access /portal context while the server is being started
>   
> Exceptions thrown:
> 15:08:25,855 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/portal].[portal]] (http-/127.0.0.1:8080-1) Servlet.service() for servlet portal threw exception: java.lang.NullPointerException
>         at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:138) [exo.jcr.framework.web-1.15.1-CP01-redhat-1.jar:1.15.1-CP01-redhat-1]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
>         at org.exoplatform.web.login.ConversationStateUpdateFilter.doFilter(ConversationStateUpdateFilter.java:66) [exo.portal.component.web.security-3.5.2.Final-redhat-4.jar:3.5.2.Final-redhat-4]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
>  
> 15:08:37,235 WARN  [org.exoplatform.web.CacheUserProfileFilter] (http-/127.0.0.1:8080-1) An error occured while cache user profile: javax.servlet.ServletException: java.lang.NullPointerException
>         at org.exoplatform.portal.application.PortalController.onService(PortalController.java:110) [exo.portal.webui.portal-3.5.2.Final-redhat-4.jar:3.5.2.Final-redhat-4]
>         at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) [exo.kernel.container-2.4.1-GA-redhat-1.jar:2.4.1-GA-redhat-1]
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-2.jar:1.0.1.Final-redhat-2]
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1-JBPAPP6-1709.jar:]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira