You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "eelaa (JIRA)" <de...@myfaces.apache.org> on 2007/12/13 03:55:43 UTC

[jira] Created: (MYFACES-1788) myfaces trinidad-demo-1.2.3 or 1.2.4 can't run well under tomcat 6.0.14

myfaces trinidad-demo-1.2.3 or 1.2.4 can't run well under tomcat 6.0.14
-----------------------------------------------------------------------

                 Key: MYFACES-1788
                 URL: https://issues.apache.org/jira/browse/MYFACES-1788
             Project: MyFaces Core
          Issue Type: Bug
          Components: JSR-252
    Affects Versions:  1.2.0
         Environment: windows xp,jdk 1.5.0.14 or 1.5.0.0,tomcat 6.0.14
            Reporter: eelaa
            Priority: Critical


The environments are:
 
(1)Windows2000(or window xp)
 
(2)Tomcat:6.0.14(setup by apache-tomcat-6.0.14.exe) or 5.5.25.
 
(3)Jjdk:1.5.0.14(we also test the program in jdk1.5.0,1.5.0_04,1.5.0_06)
 
When run the program trinidad-demo-1.2.4,we found it worked well in some PCs(windows xp or windows2000),but in other PCs(windows xp),there were some errors:
 
 
------------------------------------------------------------------------------
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet.init() for servlet faces threw exception
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
 org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
 org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
 java.lang.Thread.run(Unknown Source)
root cause
java.lang.IllegalStateException: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions!
If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml.
A typical config looks like this;
<listener>
  <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
</listener>
 javax.faces.FactoryFinder.getFactory(FactoryFinder.java:90)
 javax.faces.webapp.FacesServlet.init(FacesServlet.java:88)
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
 org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
 org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
 java.lang.Thread.run(Unknown Source)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.14 logs.
Apache Tomcat/6.0.14 
 
 trinidad-demo-1.2.3 exists the same error,but trinidad-demo-1.0.4 runs well.
 
---------------------------------------------------------------------
We googled the errors for some days,somebodies met the errors also,but we did't found any helpful information.What's the matter?
 


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