DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4524>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4524

Tomcat hangs when running as a service





------- Additional Comments From [EMAIL PROTECTED]  2001-10-31 08:14 -------
The message I got on the one install of Win2K(unfortunately was reinstalled to 
NT4) was "Visual C++ runtime error" - no error number,description, or anything. 
Then the process dies after hitting 'Ok' on the message box.

I am using jdk 1.2.2, but have upgraded to 1.3.1 and had the same problem. 
The -Xrs option didn't have any effect either.

I think the problem is in the tomcat.exe as opposed to the java classes. There 
is nothing in any of the logs once it stops responding. Nor is there anything 
useful in the Event Log(it does log that service manager has to kill the 
process when I click 'stop').

I hacked the jk_nt_service.exe/wrapper.properties from tc 3.2.3 to run tc 4.0 
as a service and it works fine so far. I found this explaination in the 
archives:
http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg35196.html

I do have Office 2k on all the machines. They also have netshield/virusscan on 
them. I have disabled the netshield service and it didn't change the results. 

The only machine that I have it running with no problems is my development 
machine which has visual studio 6(c++/vb/interdev) installed. Another developer 
with visual studio (only vb/interdev) still has the problem. I don't know if 
this is related to the problem(or coincidence) or if you are running Visual 
Studio. The error above would lead me to believe that tomcat.exe was built with 
VS, but I can not find the source/makefile for this executable. CVS contains a 
service directory, but it appears to be a unix service. Do you know where the 
source for tomcat.exe is? I can play with it to better isolate the problem.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to