• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Tomcat restart problem on production server

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello All

We are using tomcat 5.5.7 on the production server for some builds , from few days we are facing some problem of tomcat restart , we are not doing any thing on production server like restarting the tomcat it happens automatically and we are unable to find the root cause of this problem can any one help me sort out this problem.

Java Version : jdk1.5.0_16
Tomcat Version : tomcat 5.5.7

Regards

Vikas Verma

 
Ranch Hand
Posts: 2908
1
Spring Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Any log entry when Tomcat gets restarted automatically ?
 
vicky verma
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello

Just before the tomcat restart

[Unloading class sun.reflect.GeneratedConstructorAccessor43]
Exception in thread "TP-Processor27" java.lang.OutOfMemoryError: Java heap space
Sep 8, 2009 4:54:17 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
SEVERE: Caught exception (java.lang.OutOfMemoryError: Java heap space) executing org.apache.jk.common.SocketConnection@2ff76, terminating thread
Sep 8, 2009 4:56:59 PM org.apache.catalina.connector.CoyoteAdapter service
SEVERE: An exception or error occurred in the container during the request processing
java.lang.OutOfMemoryError: Java heap space

this exception appears , but after receiving this exception we have increase the memory of the tomcat but the problem has not been solved.

Regards

Vikas Verma
 
Sagar Rohankar
Ranch Hand
Posts: 2908
1
Spring Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Vikas, increasing the JVM memory in OutOfMemeory exception is not the solution, you have to find out the cause why GC is not collecting the supposed-to-be-dead objects and the classic cause of it are unclosed database connection, IO stream, sockets, etc.

Google will give plenty of results & its already discussed here many times.

And you have to change your display name.
 
Bartender
Posts: 9626
16
Mac OS X Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Sagar Rohankar wrote:Vikas, increasing the JVM memory in OutOfMemeory exception is not the solution,



Well, that depends. If you want to load 500Mb of information and you have the memory on the machine, it may be easier just to up the heap space. Of course, if loading a bunch of data isn't causing the problem, you'll have to dig deeper, and our FAQ: InvestigateOutOfMemoryError is a good starting place.

Sagar Rohankar wrote:
And you have to change your display name.



Sagar is correct. Our naming policy is here. In brief, you displayed name must be your real (or at least real-sounding) first and last name separated by a space. You can change it by clicking on "My Profile" at the top of the page.
 
Sagar Rohankar
Ranch Hand
Posts: 2908
1
Spring Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Joe Ess wrote:

Sagar Rohankar wrote:Vikas, increasing the JVM memory in OutOfMemeory exception is not the solution,


Well, that depends. If you want to load 500Mb of information and you have the memory on the machine, it may be easier just to up the heap space. Of course, if loading a bunch of data isn't causing the problem, you'll have to dig deeper,


Right Joe, I think, I should rephrase my statement like this:
Only increasing the heap memory won't solve the problem.

Joe Ess wrote:and our FAQ: InvestigateOutOfMemoryError is a good starting place.


hmm, I'm not aware of the FAQ entry.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic