How to resolve Error listenerStart when deploying web-app in Tomcat 5 5

Question

I ve deployed an Apache Wicket web-application that uses Spring and Hibernate to my Tomcat 5 5 instance  When I navigate to the Tomcat Manager interface I see that the web-application I deployed is not running  When I press  Start  I get the following error message   FAIL - Application at context path  spaghetti could not be started    My catalina log contains the following   Apr 15  2010 1 51 22 AM org apache catalina loader WebappClassLoader validateJarFile   INFO  validateJarFile  var lib tomcat5 5 webapps spaghetti WEB-INF lib jsp-api-6 0 16 jar    - jar not loaded  See Servlet Spec 2 3  section 9 7 2  Offending class  javax servlet jsp JspPage class   Apr 15  2010 1 51 22 AM org apache catalina loader WebappClassLoader validateJarFile   INFO  validateJarFile  var lib tomcat5 5 webapps spaghetti WEB-INF lib servlet-api-6 0 16 jar  - jar not loaded  See Servlet Spec 2 3  section 9 7 2  Offending class  javax servlet Servlet class   Apr 15  2010 1 51 24 AM org apache catalina core StandardContext start   SEVERE  Error listenerStart   Apr 15  2010 1 51 24 AM org apache catalina core StandardContext start   SEVERE  Context   spaghetti  startup failed due to previous errors   Excerpt from web xml         lt listener           lt listener-class              org springframework web context ContextLoaderListener          lt  listener-class       lt  listener    Any help is greatly appreciated

User · Answer

Answered provided by Tom Saleeba is very helpful. Today I also struggled with the same error

Apr 28, 2015 7:53:27 PM org.apache.catalina.core.StandardContext startInternal SEVERE: Error listenerStart

I followed the suggestion and added the logging.properties file. And below was my reason of failure:

java.lang.IllegalStateException: Cannot set web app root system property when WAR file is not expanded

The root cause of the issue was a listener (Log4jConfigListener) that I added into the web.xml. And as per the link SEVERE: Exception org.springframework.web.util.Log4jConfigListener , this listener cannot be added within a WAR that is not expanded.

It may be helpful for someone to know that this was happening on OpenShift JBoss gear.

User · Answer

I found that following these instructions helped with finding what the problem was  For me  that was the killer  not knowing what was broken   http   mythinkpond wordpress com 2011 07 01 tomcat-6-infamous-severe-error-listenerstart-message-how-to-debug-this-error   Quoting from the link      In Tomcat 6 or above  the default logger is the   java util logging    logger and not Log4J  So if you are trying to add a    log4j properties    file     this will NOT work  The Java utils logger looks for a file called    logging properties    as stated here    http   tomcat apache org tomcat-6 0-doc logging html      So to get to the debugging details create a    logging properties    file under your    WEB-INF classes    folder of your WAR and you   re all set       And now when you restart your Tomcat  you will see all of your debugging in it   s full glory         Sample logging properties file    org apache catalina core ContainerBase  Catalina  level   INFO org apache catalina core ContainerBase  Catalina  handlers   java util logging ConsoleHandler

User · Answer

I encountered this error when the JDK that I compiled the app under was different from the tomcat JVM  I verified that the Tomcat manager was running jvm 1 6 0 but the app was compiled under java 1 7 0    After upgrading Java and changing JAVA HOME in our startup script   etc init d tomcat  the error went away

User · Answer

var lib tomcat5 5 webapps spaghetti WEB-INF lib jsp-api-6 0 16 jar  var lib tomcat5 5 webapps spaghetti WEB-INF lib servlet-api-6 0 16 jar   You should not have any server-specific libraries in the  WEB-INF lib  Leave them in the appserver s own library  It would only lead to collisions in the classpath  Get rid of all appserver-specific libraries in  WEB-INF lib  and also in JRE lib and JRE lib ext if you have placed any of them there    A common cause that the appserver-specific libraries are included in the webapp s library is that starters think that it is the right way to fix compilation errors of among others the javax servlet classes not being resolveable  Putting them in webapp s library is the wrong solution  You should reference them in the classpath during compilation  i e  javac -cp  path to server lib servlet jar and so on  or if you re using an IDE  you should integrate the server in the IDE and associate the web project with the server  The IDE will then automatically take server-specific libraries in the classpath  buildpath  of the webapp project

[java] How to resolve Error listenerStart when deploying web-app in Tomcat 5.5?

Examples related to java

Examples related to spring

Examples related to deployment

Examples related to tomcat

Examples related to wicket