|
I have a similiar problem with you, I am using Tomcat 4.1.18, but currently I'm not running it as a Windows Service on Windows 2000 Server, instead I start the Tomcat service by clicking the Start Tomcat shortcut in the windows desktop.
Whenever there is a communication link error or the communication is down between the client and the server where Tomcat resides, the Tomcat service just stops by itself.
I thought the solution to my problem was to start the Tomcat as a windows service,but you stated otherwise, now I'm confused on how to fix my problem.
Is it also true that if the load is too big, the Tomcat service will automatically stop by itself?
Can anyone help us on this matter?
Thanks.
-------Original Message-------
Date: 03/08/04 17:31:40
Subject: NT Service terminates
I have Tomcat 4.1.24 running as Windows Service on Windows 2000 Server - hosting a number of applications. I currently have it running
When I run a simple load test using Microsoft Stress Tester - as I increase the load I can repeatedly force the Window Service to terminate. I'm only running with a load of 100 users.
When I run Tomcat from the command-line as an application and I repeat the test - Tomcat runs fine - performance is fine. No problems.
So what is it about running Tomcat as a service that makes it so easy to bring down? I'm tempted to blame the OS - but that doesn't really solve the problem - or explain what the difference is.
Has anyone else observed this?
Is it possible to get Tomcat to start as an application - on start-up i.e. as if it were a service - but running as an application. Sorry if that's a meaningless question.
---------------------------------
Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now
| 