• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

Tomcat has suddenly stop working

 
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Experts,

One of our Tomcat server in Production has stopped responding. Unable to see Tomcat manager. SO i tried to restart Service after cache(work,temp) clearance. No effect, then tried to restart physical server - No effect.

Checked logs , checked event viewer nothing is getting captured there as well.


Any idea, what I am missing?
 
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The only time I had Tomcat stop taking requests, it was traced to all the available request Threads hung up on an infinite wait for a resource that was not there. Discovered by using the management app before it completely hung.

Bill
 
Saloon Keeper
Posts: 23033
156
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The first thing I'd try to do is check to see if the Tomcat server ports were open, especially 8080. This can be done using the "netstat" command. For best results, shut down Tomcat and run netstat, just to make sure that some other app hasn't claimed the ports, then try again after starting Tomcat.

A look in the localhost and catalina logs for startup errors is also worth doing. And, by the way, have you made sure that the disks that hold your log and workfiles are not full?

If everything else is clean, you should try a simple web request such as "http://mytomcathost:8080/fubar.html". If you get a "404 page not found" response, then Tomcat itself is working. At that point, watch things and see if you are degrading into a situation such as the one that Bill has described. Do your tests from external boxes, just to ensure that you don't have firewall problems.

Also, note that I haven't addressed problems that can occur when Apache (or some other server) is serving as a front-end proxy to Tomcat. The rule there is first verify Tomcat itself using the above tests, then check the Apache-to-tomcat connectors.
 
Gravity is a harsh mistress. But this tiny ad is pretty easy to deal with:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic