Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Tomcat process gets killed automatically

 
Arjun Marayil
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

We are developing one element management system with its Web Client running on Tomcat. With about 50-60 users logged in, some times the tomcat server goes down. We checked the log files. The whole sequence is just like when undeploying the war file. But here the the tomcat process itself is getting killed.

We are using Sunfire V440 server with dual CPU & 4 GB memory.

Any idea why?

Thanks
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64835
86
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"Arjun CL", you have previously been warned on multiple occasions regarding adjusting your display name to meet JavaRanch standards. This is not optional, and this is your final warning. Adjust your display name to comply with the required standards prior to your next post.

Failure to comply will result in the removal of your account.

bear
JavaRanch Sheriff
 
Arjun Marayil
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I hope my new name is OK..

Some body pls give me an answer to the question I posted. We are stuck here because of this problem.
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13061
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1. What version of Tomcat is this?
2. Are you giving Tomcat more than the default memory to work with?
3. Have you customized the server.xml configuration?
4. Can you run the management application to monitor memory and Thread use?

Bill
 
Arjun Marayil
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Thanks for the reply.
1. We are using Tomcat version 5.5.12 and JDK 1.4.2_12-b03
2. We are giving 3 GB of memory for tomcat to work
3. We haven't modified server.xml file
4. Since the problem is occuring only in the client site, we wont be able to run the management application there.

Log file details:

tomcat.log
===========

[2007-03-16 14:47:36,260] - {INFO } - webclient.controller.ControllerServlet ControllerServlet : destroy called

webclient.log
==============

Pushlet[INFO] destroy(): Exit Pushlet webapp
Pushlet[INFO] Stopping 0 EventSources...
Pushlet[INFO] EventSources stopped
Pushlet[INFO] Dispatcher stopped: broadcast abort to all subscribers
Pushlet[INFO] SessionManager: Thu Mar 29 23:30:58 CEST 2007 stopped


No other extra log file entries are generated.

We are still facing the problem.
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13061
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Since the problem is occuring only in the client site, we wont be able to run the management application there.


Why not? The management app has a web interface - you just need to have an account that has the "manager" role and have the manager web app installed and you can check it any time.

Any particular reason not to upgrade to Java 1.5?

Bill
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic