Announcement Announcement Module
Collapse
No announcement yet.
Tomcat SEVERE Error: listenerStart Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Tomcat SEVERE Error: listenerStart

    I am a newbie with Spring.
    I get Tomcat listenerStart while deploying my webapp. Moreover, this deployment error is not predictable, in the sense that I do not get it every time I start Tomcat, may be 50-50 chances of getting the error or not.

    INFO: Deploying web application archive insuranceApp.war
    Sep 8, 2008 10:09:23 AM org.apache.catalina.core.StandardContext start
    SEVERE: Error listenerStart
    Sep 8, 2008 10:09:23 AM org.apache.catalina.core.StandardContext start
    SEVERE: Context [/insuranceApp] startup failed due to previous errors

    I am using Tomcat 6.0.14 with Spring 2.5.

    What can be the reason? I saw there were 2 other threads in this forum related to the exact same error, but they were being answered by newbies alike trying to guess the reason and thus not much useful.

    As a workaround, I am now using the ContextLoaderServlet and commented out ContextLoaderListener. But I would still like to know the reason why.

    <!-- <listener>
    <listener-class>
    org.springframework.web.context.ContextLoaderListe ner
    </listener-class>
    </listener> -->

    <servlet>
    <servlet-name>context</servlet-name>
    <servlet-class>org.springframework.web.context.ContextLoade rServlet</servlet-class>
    </servlet>

  • #2
    Code:
    SEVERE: Error listenerStart
    Sep 8, 2008 10:09:23 AM org.apache.catalina.core.StandardContext start
    SEVERE: Context [/insuranceApp] startup failed due to previous errors
    try enabling logging with debug or info level, the errors should appear there
    the error is not by tomcat itself, maybe a wrong bean configuration, i am telling you this
    because i remember this error years ago

    best regards

    Comment


    • #3
      Logging configuration

      web.xml

      Code:
      <context-param>
      		<param-name>log4jConfigLocation</param-name>
      		<param-value>classpath:xxs.properties</param-value>
      	</context-param>
      
      
      <listener>
      		<listener-class>org.springframework.web.util.Log4jConfigListener</listener-class>
      	</listener>
      and the xxs.properties file should be

      Code:
      log4j.rootLogger=DEBUG, stdout
      log4j.appender.stdout=org.apache.log4j.RollingFileAppender
      log4j.appender.stdout.File=c\:\\logs\\xxs_output.log
      log4j.appender.stdout.MaxBackupIndex=25
      log4j.appender.stdout.MaxFileSize=5MB
      log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
      log4j.appender.stdout.layout.ConversionPattern=[%5p:%t] [%d{ISO8601}] (%c{1}:%L) - %m%n
      log4j.logger.org.springframework=DEBUG
      log4j.logger.com.apollo=DEBUG
      log4j.logger.org.hibernate=DEBUG
      
      Regards,
      Giridhar Duggirala

      Comment


      • #4
        Thanks for the solution, I was able to get it to work.
        Actually, even without adding the log4j properties, Tomcat 6 generates logs in its logs folder. Lookin up the localhost<timestamp>.log (in my case, I am running it on my m/c) to see the causes of the errors and debugging the problem helps.

        Comment


        • #5
          Hey kasturi...Even I have same problem can you please tell me how did you solve the problem by looking at the logs...

          Comment


          • #6
            A solution

            I had the same error and could see the stack trace in the
            CATALINA_HOME/logs/localhost<date> log file

            In my case I was missing some jars, copied them in and got it working.

            Hope this helps.

            Comment


            • #7
              check dis blog

              http://skc-ebooks.blogspot.com

              i posted a systematic way to solve the error

              Comment


              • #8
                If you're deploying an unexploded war file, make sure you have set the context parameter "log4jExposeWebAppRoot" to false, otherwise the Log4jConfigurer will throw an exception while trying to get the document root folder, but somehow Tomcat won't report that exception message.

                Comment

                Working...
                X