open a command window as ntpriv or whoever the service is owned by :
set stop tomcat service name
To start :
net start tomcat service name
Mark
-Original Message-
From: Chris Daly [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 11:05 AM
To: mailto:@magic.lif.icnet.uk
Subject:
Here's the situation :
Tomcat 4.x installed as windows service running continuously at 100% cpu for no
apparent reason.
Apache forwarding requests to tomcat via jk.
I have some thread dumps that look very interesting. It appears that there is a thread
issue with jk. Open normal.txt and
I have a simple solution for you. All you need to do is create a global DataSource
then go to your context and add it as a Resource Link. You can share it between as
many contexts as you want. In Tomcat 4.x and above, this is quite simple with the
admin app ... otherwise, you have to go add it
I question whether this is a memory issue. Even if you use 600MB, why does tomcat run
at 100% cpu forever??? Shouldn't the gc finish???
I have had this same problem with Tomcat for quite some time too. It seems to be an
issue with Tomcat installed as a service ... or possibly some issue with
Howdy,
I question whether this is a memory issue. Even if you use 600MB, why
does
tomcat run at 100% cpu forever??? Shouldn't the gc finish???
GC may finish and immediately restart if memory is still full. That
would keep CPU usage pegged.
Sure, it is possible that the gc could run as long as
This sounds eerily familiar. The box I am running on is a dual processor box too.
Thanks for your info.
What else have you tried to debug this? Anything logged that looks interesting?
Mark
-Original Message-
From: Mark Prins [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2003 6:45 AM
Hello All,
I have Tomcat 4.1.18 running as a service on an NT4.0 machine with Java 1.3.1 ...
also it is getting requests via ajp13 from an apache server. It starts and works fine,
but I am seeing a problem where it gets stuck and pegs the cpu. I can still connect
to the administration page
