I had found the JVM version 1.4.0_02 (as a service) to provide random crashes, not particularly caused by load, that went away when changing to 1.4.0_04. This was with tomcat 4.1.24. I am now using 4.1.29/JDK 1.4.2_02 without a problem.
Do you have any native libraries(db?) that may be the cause of the crash? Look for an hs_err*.log file. This file should be in \%SYSTEMROOT%\system32. If the user does not have write permission to there, then it will go to the user's TEMP directory. I'm not sure about win2k, but when using Win2003 explorer's 'search' feature will not search the 'Documents and Settings' folder. This is where the user's TEMP folder is by default. I wasted waaaaaaay too much time learning this the hard way. You can use a command prompt to search the drive. Charlie -----Original Message----- From: Adrian Kristiawan [mailto:[EMAIL PROTECTED] Sent: Monday, March 08, 2004 7:52 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: NT Service terminates Importance: High 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------- From: Tomcat Users List Date: 03/08/04 17:31:40 To: Tomcat 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 ____________________________________________________ IncrediMail - Email has finally evolved - Click Here
