Announcement Announcement Module
Collapse
No announcement yet.
Application Context Keeps Reloading Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Application Context Keeps Reloading

    Hi, I have a Spring 2.5.6 MVC app running on Tomcat 6, Java 6. It seems that the ApplicationContexts keeps reloading over and over. The output is bellow. I dont know if it has anything to do with the no appenders found message that I keep getting, but I dont think that has to do with it. Has anyone ever seen this?

    INFO: Starting service Catalina
    Dec 31, 2009 11:46:32 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
    log4j:WARN No appenders could be found for logger (org.springframework.web.servlet.DispatcherServlet ).
    log4j:WARN Please initialize the log4j system properly.
    Dec 31, 2009 11:46:33 AM org.apache.catalina.core.ApplicationContext log
    INFO: Initializing Spring FrameworkServlet 'springmvc'
    Dec 31, 2009 11:46:33 AM org.apache.coyote.http11.Http11Protocol start
    INFO: Starting Coyote HTTP/1.1 on http-8080
    Dec 31, 2009 11:46:34 AM org.apache.jk.common.ChannelSocket init
    INFO: JK: ajp13 listening on /0.0.0.0:8009
    Dec 31, 2009 11:46:34 AM org.apache.jk.server.JkMain start
    INFO: Jk running ID=0 time=0/63 config=null
    Dec 31, 2009 11:46:34 AM org.apache.catalina.startup.Catalina start
    INFO: Server startup in 2004 ms
    Dec 31, 2009 11:46:43 AM org.apache.catalina.loader.WebappClassLoader modified
    INFO: Additional JARs have been added : 'jms-1.1.jar'
    Dec 31, 2009 11:46:43 AM org.apache.catalina.core.StandardContext reload
    INFO: Reloading this Context has started
    Dec 31, 2009 11:46:43 AM org.apache.catalina.core.ApplicationContext log
    INFO: Destroying Spring FrameworkServlet 'springmvc'
    log4j:WARN No appenders could be found for logger (org.springframework.web.servlet.DispatcherServlet ).
    log4j:WARN Please initialize the log4j system properly.
    Dec 31, 2009 11:46:44 AM org.apache.catalina.core.ApplicationContext log
    INFO: Initializing Spring FrameworkServlet 'springmvc'
    Dec 31, 2009 11:46:55 AM org.apache.catalina.loader.WebappClassLoader modified
    INFO: Additional JARs have been added : 'jms-1.1.jar'
    Dec 31, 2009 11:46:55 AM org.apache.catalina.core.StandardContext reload
    INFO: Reloading this Context has started
    Dec 31, 2009 11:46:55 AM org.apache.catalina.core.ApplicationContext log
    INFO: Destroying Spring FrameworkServlet 'springmvc'
    log4j:WARN No appenders could be found for logger (org.springframework.web.servlet.DispatcherServlet ).
    log4j:WARN Please initialize the log4j system properly.
    Dec 31, 2009 11:46:56 AM org.apache.catalina.core.ApplicationContext log
    INFO: Initializing Spring FrameworkServlet 'springmvc'
    Dec 31, 2009 11:47:07 AM org.apache.catalina.loader.WebappClassLoader modified
    INFO: Additional JARs have been added : 'jms-1.1.jar'
    Dec 31, 2009 11:47:07 AM org.apache.catalina.core.StandardContext reload
    INFO: Reloading this Context has started
    Dec 31, 2009 11:47:07 AM org.apache.catalina.core.ApplicationContext log
    INFO: Destroying Spring FrameworkServlet 'springmvc'
    log4j:WARN No appenders could be found for logger (org.springframework.web.servlet.DispatcherServlet ).
    log4j:WARN Please initialize the log4j system properly.
    Dec 31, 2009 11:47:07 AM org.apache.catalina.core.ApplicationContext log

  • #2
    Pretty much what I see happening here is the Spring FramworkServlet is being destroyed and then re-instantiated and then initialized. What I don't get is why. This happens about once every 5 seconds.

    Has no one really never seen this before? I have a pretty basic setup going. Spring 2.5.6, Tiles 2.1 Hibernate 3.3 (not coupled to spring), Java 6, Tomcat 6, working in eclipse j2ee version.

    Comment


    • #3
      i just started seeing this happen as well. i am not sure what is causing it, as the app i've been developing has been working fine until now.

      i can say that this only appears to happen in eclipse/tomcat. when i run my war as a stand-alone tomcat app, it does not reload over and over.

      this pretty much makes debugging impossible, currently. any help from any seniors would be greatly appreciated.

      regards,

      jason

      Comment


      • #4
        I'm also facing exactly the same problem. Interestingly, when I manually delete the jms-1.1 jar from the eclipse build directory, tomcat startup is successful (although problem re-emerges when maven plugin re-downloads the dependency).
        Has anyone managed to identify the root-cause of the issue?
        Cheers,
        Stephen

        Comment


        • #5
          Guys, I think I've found the problem in my instance.
          It appears that the jms-1.1.jar being downloaded from maven2 repository is corrupt - the compiled jar retrieved from maven2 respository is only 370bytes.
          After manually downloading the jms jar from https://cds.sun.com/is-bin/INTERSHOP...BundleDownload and copying into the repository, I no longer get the issue above in Eclipse when starting tomcat server. Definitely worth checking this if you are using maven2.

          Additionally, just from reading some other posts, you may want to check file permissions on the impacted jars, as this could be another root cause.

          Hope this info helps.
          Cheers,
          Stephen

          Comment


          • #6
            Log4j 1.2.15 and JMX

            http://onemanwenttomow.wordpress.com...-dependencies/

            Solved the problem for me.

            Comment


            • #7
              Skant,
              You saved my day after 2 long days!!!!
              I simply renamed related jms jars... Thats it!!!! At least I can continue. Otherwise, each click was taking long...
              Thanks!

              Originally posted by skant View Post
              Guys, I think I've found the problem in my instance.
              It appears that the jms-1.1.jar being downloaded from maven2 repository is corrupt - the compiled jar retrieved from maven2 respository is only 370bytes.
              After manually downloading the jms jar from https://cds.sun.com/is-bin/INTERSHOP...BundleDownload and copying into the repository, I no longer get the issue above in Eclipse when starting tomcat server. Definitely worth checking this if you are using maven2.

              Additionally, just from reading some other posts, you may want to check file permissions on the impacted jars, as this could be another root cause.

              Hope this info helps.
              Cheers,
              Stephen

              Comment

              Working...
              X