I reverted to using the org.apache.catalina.connector.http.HttpConnector
instead of the org.apache.coyote.tomcat4.CoyoteConnector, now it works just
fine.
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
Citeren Jake Robb [EMAIL PROTECTED]:
The very first thing I'd try is upgrading to the latest version of the
JDK (1.4.1_01).
1.4.1_02 is the latest.
I have had this problem with 4.0.6 running standalone with 1.3.x Upgrading
to 1.4.1_01 helped.
I have a NT4 box with 4.0.6 standalone on
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
- the logs show nothing strange; I've set up with request dumping now
- I'm playing with the params for the tomcat.exe in the registry (-Xrs, JVM
dll, garbage collection options)
- traffic is really low but that doesn't seem to make a difference.
This afternoon it seems to be behaving itself...
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
There is an issue with the JDK 1.3.x and NT running as a service? Maybe try
and upgrade the jdk to 1.4?
Jeremy Davis
Senior Support Analyst
BPI Marketplace Integration
614.760.8941
1.800.436.8726 - Support Line
-Original Message-
From: Strecker, Mark [mailto:[EMAIL PROTECTED]
Sent:
The very first thing I'd try is upgrading to the latest version of the JDK
(1.4.1_01). I thought Tomcat 4.x required it -- I'm surprised you got as
far as you did!
-Jake
- Original Message -
From: Strecker, Mark [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday,
