• 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 service halting with no apparent error

 
Greenhorn
Posts: 1
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Greetings all. I'm new to the Ranch and to the Saloon, but I decided I would pose this question here, since I haven't been able to find any answers anywhere else - inluding from the guy who taught us our Tomcat Administration class.

Here's the basic situation:

We have Tomcat 5.5.26 running on Windows 2003 Standard Server with a quad core processor and 4 GB of RAM. We allocate 1024 MB of RAM to the JVM, and have the following thread allocations in the server.xml file:

maxThreads="250" minSpareThreads="25" maxSpareThreads="75"

Essentially what happens is this:

The server is running along fine, and then all of a sudden, for no apparent reason that we can find, the server shuts down. The timing does not seem to coincide with any stack trace, and it not only kills the server, it kills the Windows Service with the following error:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 1/28/2009
Time: 9:33:19 AM
User: N/A
Description:
The Apache Tomcat service terminated unexpectedly. It has done this 1 time(s).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


When we crawl through the catalina and tomcat stdout and stderr logs, we do not get any stack traces around those times - it's like the entire JVM just packed up and died. If we restart the service, it comes right back, and we can use the server immediately, with no apparent ill effects.

This has been an intermittent problem for at least 6 months, and we haven't been able to recreate it through any combination of server stress and/or bad code. Nothing I can seem to do manually makes the server behave this way, and I'd be thoroughly greatful for any suggestions on tracking this down. Thanks in advance.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic