No, there was no any hot deployment. We deploy our application WAR file and restart tomcat. This is a must for us. And there was no any change to Log4J library jar file.
BR, Shahnaz Ali. On Thu, Apr 8, 2010 at 12:13 PM, Yair Ogen <yairo...@gmail.com> wrote: > Hot deploy is when you load a new version of a war for example while the > server is still running. This triggers a chain of init actions on the > server > side. > > I see from the logs the doGet method in the servlet caused a init of log4j > configuration. > > try looking in that direction. I think this should not happen. > > The exception logged indicates a class file was changed in the middle of > using it (or something like that). these things sometime happen when using > hot deploy. > > On Wed, Apr 7, 2010 at 4:40 PM, Shahnaz Ali <shaan20...@gmail.com> wrote: > > > Hi, > > > > Thanks for your quick response. > > > > This crash happens only once so far in a year. After restart of OS and > > Tomcat, without any change system is working fine again. This is a telco > > system, so they need to know reason of crash. And if possible solution of > > that. > > > > Actually this is a server side application which receives calls. At one > > time > > it may receive around 150 concurrent calls. When I check logs, i notice > > there were around 900 call sessions. No clue how it happened. > > > > Application is in production, so we just cant change the configuration so > > easily. We haven't tried with Java 6. > > > > Current Log4J version is: log4j-1.2.8.jar > > Java Version is: 1.5 > > OS: Redhat Linux > > > > Please explain, what do you mean by "hot deploy" here? > > > > > > BR, > > Shahnaz Ali. > > > > > > > > On Wed, Apr 7, 2010 at 6:10 PM, Michael Erskine <mse...@googlemail.com > > >wrote: > > > > > On 7 April 2010 13:19, Shahnaz Ali <shaan20...@gmail.com> wrote: > > > > We have IVR application running on tomcat web application server on > > > Redhat > > > > linux OS, using Log4J. This is a mission critical server application > > with > > > > good amount of call load. > > > > > > > > Recently we faced JVM (tomcat) crash and major of errors before crash > > > > pointing to Log4J. We are not expert in Log4J, though of sharing with > > you > > > > and take your feedback. If you can point out the reason and > corrective > > > > action, will be great. > > > > > > Tomcat running as root? 1080 threads? :o > > > > > > I can see the PropertyConfigurator failing repeatedly - once for each > > > HTTP daemon? > > > Is this something to do with... > > > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > > > > > > Does this Log4j configuration usually work? > > > Have you tried running on a recent version of Java 6? > > > > > > Regards, > > > Michael Erskine. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > > > For additional commands, e-mail: log4j-user-h...@logging.apache.org > > > > > > > > >
