COURSE of the MONTH

Problems running deployed app on Tomcat server .

How or Where is the context root for an application that has been built in Eclipse as a Maven Webapp and deployed to a Apache Tomcat/6.0.36 server defined?

The War file was created with the following command: mvn clean compile package. The War(adminDev.war) has been deployed to the server via the Tomcat Manager. After deployment is complete when I click on the Application path shown in the manager ( /adminDev) I am getting a 404 with the following message: "The requested URL /adminDev/ was not found on this server."

We thought the context root is defined by the server at deployment and would be defined by the war file name?

We have not done much on Tomcat recently so this may be something obvious just not to us.

Sorry about the delay in getting a comment out there .... finally back from a week long florida vacation:)

Attached below is the web.xml ..... Again this is a maven project web app deployed to a Tomcat server. I do not see anything in the previous web.xm file that defines that context root to run the app? When we attempt to run the deployed app from the remote Tomcat server we are getting the following Msg: "The requested URL /adminDev/ was not found on this server." The name of the War file is adminDev.War.

We do, our index.xhtml resides in our webapp project directory .... attached is our index.xhtml below. Can you give me a little more info then "You need to have index.xhtml in your project". What does the index.xhtml file have to do with the context root of the app running on Tomcat?

check catalina.out. it seems you have managed to deploy it in ROOT webapp...

0

West100Author Commented: 2014-02-24

Just to review .....After we click on the app Path shown in the Tomcat Web Application Manager the following message appears in firefox:

404 Not Found
Not Found
The requested URL /efacAdminDev/ was not found on this server.

The catalina.out file on the Tomcat server only shows the following :

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)

Again after the efacAdminDev.WAR is created locally via: mvn clean compile package. We logged onto the Tomcat Web Application Manager and from the manager section "WAR file to deploy" we selected the WAR file created then selected Deploy.

We are running Apache Tomcat/6.0.36. I have found the catalina.out. What are you hoping to see in catalina.out?

When I try to run the application from the Tomcat Manager nothing is written to catalina.out. The browser shows the following message:"Not Found
The requested URL /adminDev/ was not found on this server."

This deployment is with adminDev being the name of the War file deployed and started on Tomcat.

When I stop and restart the app from the manager the following messages are written to catalina.out.

What did you mean you when wrote "it seems you have managed to deploy it in ROOT webapp... " ? When deploying the app with the manager should I be including something to the name of the war file ?

Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbcSEVERE: The web application [/adminDev] registered the JDBC driver [oracle.jdbc.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [systemRoleBeanCache.data] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [Timer-9] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [Timer-10] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-1] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-2] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-3] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-4] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-5] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-6] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-7] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-8] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-9] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-10] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-11] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-12] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-13] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-14] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-15] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-16] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-17] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-18] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-19] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-20] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-21] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-22] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-23] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: The web application [/adminDev] appears to have started a thread named [UCP-worker-thread-24] but has failed to stop it. This is very likely to create a memory leak.Feb 25, 2014 10:13:40 AM org.apache.catalina.loader.WebappClassLoader validateJarFileINFO: validateJarFile(/usr/local/tomcat6/webapps/adminDev/WEB-INF/lib/geronimo-servlet_3.0_spec-1.0.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.classFeb 25, 2014 10:13:40 AM org.apache.catalina.loader.WebappClassLoader validateJarFileINFO: validateJarFile(/usr/local/tomcat6/webapps/adminDev/WEB-INF/lib/servlet-api-6.0.35.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.classFeb 25, 2014 10:13:47 AM com.sun.faces.config.ConfigureListener contextInitializedINFO: Initializing Mojarra 2.1.20 ( 20130304-1520 https://svn.java.net/svn/mojarra~svn/tags/2.1.20@11693) for context '/adminDev'Feb 25, 2014 10:13:48 AM com.sun.faces.config.processor.FaceletTaglibConfigProcessor processComponentWARNING: JSF1029: Application is versioned at 2.0 (either explicitly by the version of /WEB-INF/faces-config.xml or the lack of a /WEB-INF/faces-confg.xml), however class 'org.apache.myfaces.custom.aliasbean.AliasBeanTagHandler' depends on a legacy facelet class. The facelet artifact represented by this class will not be registered.Feb 25, 2014 10:13:48 AM com.sun.faces.config.processor.FaceletTaglibConfigProcessor processComponentWARNING: JSF1029: Application is versioned at 2.0 (either explicitly by the version of /WEB-INF/faces-config.xml or the lack of a /WEB-INF/faces-confg.xml), however class 'org.apache.myfaces.custom.aliasbean.AliasBeansScopeTagHandler' depends on a legacy facelet class. The facelet artifact represented by this class will not be registered.Feb 25, 2014 10:13:48 AM com.sun.faces.config.processor.FaceletTaglibConfigProcessor processComponentWARNING: JSF1029: Application is versioned at 2.0 (either explicitly by the version of /WEB-INF/faces-config.xml or the lack of a /WEB-INF/faces-confg.xml), however class 'org.apache.myfaces.custom.schedule.ScheduleTagHandler' depends on a legacy facelet class. The facelet artifact represented by this class will not be registered.Feb 25, 2014 10:13:48 AM com.sun.faces.config.processor.FaceletTaglibConfigProcessor processComponentWARNING: JSF1029: Application is versioned at 2.0 (either explicitly by the version of /WEB-INF/faces-config.xml or the lack of a /WEB-INF/faces-confg.xml), however class 'org.apache.myfaces.custom.tabbedpane.HtmlPanelTabbedPaneTagHandler' depends on a legacy facelet class. The facelet artifact represented by this class will not be registered.Feb 25, 2014 10:13:48 AM com.sun.faces.config.processor.FaceletTaglibConfigProcessor processComponentWARNING: JSF1029: Application is versioned at 2.0 (either explicitly by the version of /WEB-INF/faces-config.xml or the lack of a /WEB-INF/faces-confg.xml), however class 'org.apache.myfaces.custom.tree.taglib.TreeTagHandler' depends on a legacy facelet class. The facelet artifact represented by this class will not be registered.Feb 25, 2014 10:13:48 AM com.sun.faces.config.processor.FaceletTaglibConfigProcessor processHandlerClassWARNING: JSF1029: Application is versioned at 2.0 (either explicitly by the version of /WEB-INF/faces-config.xml or the lack of a /WEB-INF/faces-confg.xml), however class '[handler-class: null]' depends on a legacy facelet class. The facelet artifact represented by this class will not be registered.Feb 25, 2014 10:13:48 AM com.sun.faces.config.processor.FaceletTaglibConfigProcessor processHandlerClassWARNING: JSF1029: Application is versioned at 2.0 (either explicitly by the version of /WEB-INF/faces-config.xml or the lack of a /WEB-INF/faces-confg.xml), however class '[handler-class: null]' depends on a legacy facelet class. The facelet artifact represented by this class will not be registered.Feb 25, 2014 10:13:48 AM com.sun.faces.config.processor.FaceletTaglibConfigProcessor processHandlerClassWARNING: JSF1029: Application is versioned at 2.0 (either explicitly by the version of /WEB-INF/faces-config.xml or the lack of a /WEB-INF/faces-confg.xml), however class '[handler-class: null]' depends on a legacy facelet class. The facelet artifact represented by this class will not be registered.Feb 25, 2014 10:13:48 AM com.sun.faces.config.processor.FaceletTaglibConfigProcessor processHandlerClassWARNING: JSF1029: Application is versioned at 2.0 (either explicitly by the version of /WEB-INF/faces-config.xml or the lack of a /WEB-INF/faces-confg.xml), however class '[handler-class: null]' depends on a legacy facelet class. The facelet artifact represented by this class will not be registered.Feb 25, 2014 10:13:48 AM org.primefaces.webapp.PostConstructApplicationEventListener processEventINFO: Running on PrimeFaces 3.5Feb 25, 2014 10:13:48 AM com.sun.faces.config.ConfigureListener$WebConfigResourceMonitor$Monitor <init>INFO: Monitoring jndi:/localhost/adminDev/WEB-INF/faces-config.xml for modifications