RE: Need help with tomcat running as service with ajp13

2003-03-20 Thread Davis, Jeremy
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: Thursday, March 20, 2003 4:15 PM
To: Tomcat Users List
Subject: Need help with tomcat running as service with ajp13


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 and connect to
applications in a reasonable amount of time, but I am concerned about why it
is using 100% cpu to do nothing.
   Has anyone experienced this or have a suggestion as to what I can log to
figure out what is happening? (I have tried to log everything with no
success.)

TIA,
Mark

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

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



Re: Need help with tomcat running as service with ajp13

2003-03-20 Thread Jake Robb
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, March 20, 2003 4:15 PM
Subject: Need help with tomcat running as service with ajp13


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 and connect to
applications in a reasonable amount of time, but I am concerned about why it
is using 100% cpu to do nothing.
   Has anyone experienced this or have a suggestion as to what I can log to
figure out what is happening? (I have tried to log everything with no
success.)

TIA,
Mark

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


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



Re: Need help with tomcat running as service with ajp13

2003-03-21 Thread Mark Prins
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 1.4.1_02 with coyote connector 
RC1 that has this behaviour (cpu hogging) (I upgraded the JDK from 
1.4.1_01 - but that doesn't seem to help)
Both are dual processor boxes...

Mark


--
_
Zon Breedband Family, 2 keer zo snel als alle andere ADSL aanbieders.
Voor maar 34 euro per maand. Bestel nu op www.zonnet.nl/breedband
Tijdelijk gratis modem en geen aansluitkosten!

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



RE: Need help with tomcat running as service with ajp13

2003-03-21 Thread Strecker, Mark
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
To: Tomcat Users List; Jake Robb
Subject: Re: Need help with tomcat running as service with ajp13


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 1.4.1_02 with coyote connector 
RC1 that has this behaviour (cpu hogging) (I upgraded the JDK from 
1.4.1_01 - but that doesn't seem to help)
Both are dual processor boxes...

Mark


--
_
Zon Breedband Family, 2 keer zo snel als alle andere ADSL aanbieders.
Voor maar 34 euro per maand. Bestel nu op www.zonnet.nl/breedband
Tijdelijk gratis modem en geen aansluitkosten!

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


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



RE: Need help with tomcat running as service with ajp13

2003-03-21 Thread Mark Prins
- 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... but it can take upto a day 
to go wrong. 

Mark



Citeren "Strecker, Mark" <[EMAIL PROTECTED]>:

> 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
> To: Tomcat Users List; Jake Robb
> Subject: Re: Need help with tomcat running as service with ajp13
> 
> 
> 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 1.4.1_02 with coyote connector
> 
> RC1 that has this behaviour (cpu hogging) (I upgraded the JDK from 
> 1.4.1_01 - but that doesn't seem to help)
> Both are dual processor boxes...
> 
> Mark
> 
> 
> --
> _
> Zon Breedband Family, 2 keer zo snel als alle andere ADSL aanbieders.
> Voor maar 34 euro per maand. Bestel nu op www.zonnet.nl/breedband
> Tijdelijk gratis modem en geen aansluitkosten!
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 



--
_
Zon Breedband Family, 2 keer zo snel als alle andere ADSL aanbieders.
Voor maar 34 euro per maand. Bestel nu op www.zonnet.nl/breedband
Tijdelijk gratis modem en geen aansluitkosten!

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



RE: Need help with tomcat running as service with ajp13

2003-03-28 Thread Mark Prins
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 debug this? Anything logged that looks 
> interesting?
> 
> Mark
> 
> -Original Message-
> From: Mark Prins [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 21, 2003 6:45 AM
> To: Tomcat Users List; Jake Robb
> Subject: Re: Need help with tomcat running as service with ajp13
> 
> 
> 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 1.4.1_02 with coyote connector 
> RC1 that has this behaviour (cpu hogging) (I upgraded the JDK from 
> 1.4.1_01 - but that doesn't seem to help)
> Both are dual processor boxes...
> 





--
_
Zon Breedband Family, 2 keer zo snel als alle andere ADSL aanbieders.
Voor maar 34 euro per maand. Bestel nu op www.zonnet.nl/breedband
Tijdelijk gratis modem en geen aansluitkosten!

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