You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Freek Segers (JIRA)" <de...@myfaces.apache.org> on 2009/02/18 11:49:01 UTC
[jira] Created: (MYFACES-2153) Exception in initialization of
FacesServletMappings in WebXml.java
Exception in initialization of FacesServletMappings in WebXml.java
------------------------------------------------------------------
Key: MYFACES-2153
URL: https://issues.apache.org/jira/browse/MYFACES-2153
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 1.1.5
Reporter: Freek Segers
When the first requests to .jspx (facelets) pages, after starting the web application, are concurrent an exception occurs in WebXml.java.
It is a little hard to reproduce but I strongly feel that this is a concurrency issue. The stack trace below shows two threads requesting a .jspx page within 20 milliseconds.
[2/18/09 7:52:33:058 GMT+01:00] 0000002c viewhandler E Error Rendering View[/bundles/applications/jsf/applicationValidations.jspx]
java.lang.ArrayIndexOutOfBoundsException
at java.util.ArrayList.ensureCapacity(ArrayList.java:196)
at java.util.ArrayList.add(ArrayList.java:377)
at org.apache.myfaces.shared_impl.webapp.webxml.WebXml.getFacesServletMappings(WebXml.java:130)
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getServletMapping(JspViewHandlerImpl.java:347)
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getViewIdPath(JspViewHandlerImpl.java:294)
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getActionURL(JspViewHandlerImpl.java:158)
at com.sun.facelets.FaceletViewHandler.getActionURL(FaceletViewHandler.java:786)
[2/18/09 7:52:33:071 GMT+01:00] 0000002f viewhandler E Error Rendering View[/bundles/synonym/jsf/resolvesynonym.jspx]
java.lang.NullPointerException
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getServletMapping(JspViewHandlerImpl.java:374)
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getViewIdPath(JspViewHandlerImpl.java:294)
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getActionURL(JspViewHandlerImpl.java:158)
at com.sun.facelets.FaceletViewHandler.getActionURL(FaceletViewHandler.java:786)
Every .jspx file requested after this results in the same NPE as the last thread of the stack trace above. Restaring the application usually fixes the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2153) Exception in initialization of
FacesServletMappings in WebXml.java
Posted by "Freek Segers (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675371#action_12675371 ]
Freek Segers commented on MYFACES-2153:
---------------------------------------
Just found out that the software that has this problem is running an old version of MyFaces.
Closing the issue for now.
> Exception in initialization of FacesServletMappings in WebXml.java
> ------------------------------------------------------------------
>
> Key: MYFACES-2153
> URL: https://issues.apache.org/jira/browse/MYFACES-2153
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.1.1
> Reporter: Freek Segers
>
> When the first requests to .jspx (facelets) pages, after starting the web application, are concurrent an exception occurs in WebXml.java.
> It is a little hard to reproduce but I strongly feel that this is a concurrency issue. The stack trace below shows two threads requesting a .jspx page within 20 milliseconds.
> [2/18/09 7:52:33:058 GMT+01:00] 0000002c viewhandler E Error Rendering View[/bundles/applications/jsf/applicationValidations.jspx]
> java.lang.ArrayIndexOutOfBoundsException
> at java.util.ArrayList.ensureCapacity(ArrayList.java:196)
> at java.util.ArrayList.add(ArrayList.java:377)
> at org.apache.myfaces.shared_impl.webapp.webxml.WebXml.getFacesServletMappings(WebXml.java:130)
> at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getServletMapping(JspViewHandlerImpl.java:347)
> at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getViewIdPath(JspViewHandlerImpl.java:294)
> at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getActionURL(JspViewHandlerImpl.java:158)
> at com.sun.facelets.FaceletViewHandler.getActionURL(FaceletViewHandler.java:786)
> [2/18/09 7:52:33:071 GMT+01:00] 0000002f viewhandler E Error Rendering View[/bundles/synonym/jsf/resolvesynonym.jspx]
> java.lang.NullPointerException
> at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getServletMapping(JspViewHandlerImpl.java:374)
> at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getViewIdPath(JspViewHandlerImpl.java:294)
> at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getActionURL(JspViewHandlerImpl.java:158)
> at com.sun.facelets.FaceletViewHandler.getActionURL(FaceletViewHandler.java:786)
> Every .jspx file requested after this results in the same NPE as the last thread of the stack trace above. Restaring the application usually fixes the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.