Re: JVM crash with Log4J.

2010-04-08 Thread Shahnaz Ali
We have test server but how we will create actual load on that. Recreating this problem is a challenge. After restarting, its working fine from last around 3 weeks. One server receives 80,000 call requests in a day on average. Since then no issue It is basically serving VXML for telephony calls

Re: JVM crash with Log4J.

2010-04-08 Thread Michael Erskine
On 8 April 2010 10:27, Shahnaz Ali wrote: > Its not possible to do these kind of experiments in running production > server. But i am sure there is nothing happened like redeploying new war, > jar or any kind of change. Server was untouched for last several hours. Don't you have an identical test

Re: JVM crash with Log4J.

2010-04-08 Thread Shahnaz Ali
Hi, Its not possible to do these kind of experiments in running production server. But i am sure there is nothing happened like redeploying new war, jar or any kind of change. Server was untouched for last several hours. Logs are not fabricated, yeah i took only the portion when problem started.

Re: JVM crash with Log4J.

2010-04-08 Thread Michael Erskine
On 8 April 2010 07:47, Shahnaz Ali wrote: > No, there was no any hot deployment. But the evidence points to a change of class so something equivalent to a redeployment must have happened. Something caused a deployed class to be reloaded and that operation failed due to a class incompatibility. Th

Re: JVM crash with Log4J.

2010-04-07 Thread Shahnaz Ali
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 wrote: > Hot deploy is when you load a new version of a war for

Re: JVM crash with Log4J.

2010-04-07 Thread Yair Ogen
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

Re: JVM crash with Log4J.

2010-04-07 Thread Shahnaz Ali
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 appli

Re: JVM crash with Log4J.

2010-04-07 Thread Michael Erskine
On 7 April 2010 13:19, Shahnaz Ali 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 >

Re: JVM crash with Log4J.

2010-04-07 Thread Yair Ogen
are you using hot deploy on Tomcat? which version of log4j are you using? On Wed, Apr 7, 2010 at 3:19 PM, Shahnaz Ali wrote: > Hi, > > 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 am

JVM crash with Log4J.

2010-04-07 Thread Shahnaz Ali
Hi, 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, t