Tomcat 3.3.1a problem

[Marko Krejic <ma...@enovation.se>]

Hi,
 
We are running Tomcat 3.3.1a on a Windows Server 2003. A apache server is also installed on the machine as a proxy and it is connected with the tomcat through AJP12. Tomcat is running on JDK1.4.2_13.
 
 
Now to our problem. We have been running this setup for quite a while (a few years). But until recently, the load has increased. 
It seems like when there are quite many connections, then suddenly it is not possible to read the requestbody anymore. We get the request and we are seeing the request header, but when we want to read the body, it all seems to hang... At this time it seems like the threads are just stacking up and nothing is processed.
 
Other threads, such as timer-threads and file-listener threads, are running normally. It seems like only the request comming through the connectors (the AJP12 and HTTP) are hanging. 
 
Does anybody recognise these problems? And does anybody have any suggestions about how to fix this? 
 
We have tried to run without Apache and AJP12, but we got the same problem. 
 
I could mention that we know that we have mobile clients sending requests to the server and if the server is not responding within a certain time, they will "cut-off" the request. Could it be that tomcat is not "releasing" these requests? 
 
Please, any suggestions would be very apprieciated! 
 
Thanks in advance! 
 
Marko Krejic

Re: Tomcat 3.3.1a problem

[Pid <p...@pidster.com>]

Bill Barker wrote:
> I don't recognize the problem, but AJP12 was deprecated even for 3.3.1a 
> (which, for Pid's benifit, was a single security issue bugfix release from 
> 3.3.1).  

Hat duly tipped.

p

> 
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: Tomcat 3.3.1a problem

[Bill Barker <wb...@wilshire.com>]

I don't recognize the problem, but AJP12 was deprecated even for 3.3.1a 
(which, for Pid's benifit, was a single security issue bugfix release from 
3.3.1).  In any case, it will be a bottleneck for any attempt to scale your 
application.  You should try with the AJP13 connector, which works better on 
3.3.1a then either the AJP12 connector or the HTTP/1.0 connector (the 
HTTP/1.0 connector in particular is known to have issues on Windows).  If 
you can set up a test environment, the other thing to try is 3.3.2 with the 
CoyoteConnector (either AJP13 or HTTP/1.1).  Short-term it is probably less 
painful than upgrading to TC 5.5.x or TC 6.0.x.

Additional information I'd like to see is the mod_jk version (AJP12, while 
still shipping with the most recent mod_jk hasn't been supported in a very 
long time.  It wouldn't surprise me at all if it is broken on recent 
versions), and a thread dump if you can get one.  Also turning up your 
JkLogLevel to debug on mod_jk might help.

As Mark noted, 3.3.x is still somewhat officially supported (although I have 
trouble seeing what would trigger a 3.3.3 release, even if it does have some 
goodies in it :).  If you can get the thread dump and/or the debug mod_jk 
logs, it may be better if you open a BZ report and attect them there, so 
they are easier for me to find.

"Marko Krejic" <ma...@enovation.se> wrote in message 
news:4AED0E970814CF4DABF0DAB27D5C6736D4BB@drno.EnovationAB.local...
Hi,

We are running Tomcat 3.3.1a on a Windows Server 2003. A apache server is 
also installed on the machine as a proxy and it is connected with the tomcat 
through AJP12. Tomcat is running on JDK1.4.2_13.


Now to our problem. We have been running this setup for quite a while (a few 
years). But until recently, the load has increased.
It seems like when there are quite many connections, then suddenly it is not 
possible to read the requestbody anymore. We get the request and we are 
seeing the request header, but when we want to read the body, it all seems 
to hang... At this time it seems like the threads are just stacking up and 
nothing is processed.

Other threads, such as timer-threads and file-listener threads, are running 
normally. It seems like only the request comming through the connectors (the 
AJP12 and HTTP) are hanging.

Does anybody recognise these problems? And does anybody have any suggestions 
about how to fix this?

We have tried to run without Apache and AJP12, but we got the same problem.

I could mention that we know that we have mobile clients sending requests to 
the server and if the server is not responding within a certain time, they 
will "cut-off" the request. Could it be that tomcat is not "releasing" these 
requests?

Please, any suggestions would be very apprieciated!

Thanks in advance!

Marko Krejic




---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: Tomcat 3.3.1a problem

[Pid <p...@pidster.com>]

Mark Thomas wrote:
> Pid wrote:
>> Marko Krejic wrote:
>>> Hi,
>>>  
>>> We are running Tomcat 3.3.1a on a Windows Server 2003. A apache server is also installed on the machine as a proxy and it is connected with the tomcat through AJP12. Tomcat is running on JDK1.4.2_13.
>> The silence you experienced is people being dumbfounded that you're
>> running Tomcat 3 (versions up to and including 5.0 are now no longer
>> supported) 
> 
> This is not the case. Whilst 5.0.x is unsupported, 4.1.x is still supported
> (and will be for some time) and technically so is 3.3.x although 3.3.x is
> next on my list of things to ask the dev list if we want to de-support.

Lordy. I had no idea...

p

> and AJP12.  Tomcat 3 is ancient.
> 
> Indeed ;)
> 
> Mark
> 
> 
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: Tomcat 3.3.1a problem

[Mark Thomas <ma...@apache.org>]

Pid wrote:
> Marko Krejic wrote:
>> Hi,
>>  
>> We are running Tomcat 3.3.1a on a Windows Server 2003. A apache server is also installed on the machine as a proxy and it is connected with the tomcat through AJP12. Tomcat is running on JDK1.4.2_13.
> 
> The silence you experienced is people being dumbfounded that you're
> running Tomcat 3 (versions up to and including 5.0 are now no longer
> supported) 

This is not the case. Whilst 5.0.x is unsupported, 4.1.x is still supported
(and will be for some time) and technically so is 3.3.x although 3.3.x is
next on my list of things to ask the dev list if we want to de-support.

and AJP12.  Tomcat 3 is ancient.

Indeed ;)

Mark


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: Tomcat 3.3.1a problem

[Pid <p...@pidster.com>]

Marko Krejic wrote:
> Hi,
>  
> We are running Tomcat 3.3.1a on a Windows Server 2003. A apache server is also installed on the machine as a proxy and it is connected with the tomcat through AJP12. Tomcat is running on JDK1.4.2_13.

The silence you experienced is people being dumbfounded that you're
running Tomcat 3 (versions up to and including 5.0 are now no longer
supported) and AJP12.  Tomcat 3 is ancient.

(I'm hoping that the 'a' doesn't mean an alpha version.)

> Now to our problem. We have been running this setup for quite a while (a few years). But until recently, the load has increased. 
> It seems like when there are quite many connections, then suddenly it is not possible to read the requestbody anymore. We get the request and we are seeing the request header, but when we want to read the body, it all seems to hang... At this time it seems like the threads are just stacking up and nothing is processed.

... on the same server hardware one could presume?
Could just be that your load is now too much for the server.

If the application hasn't changed but things were previously stable, and
the load has increased, then the thing that has changed is likely to
lead you to the cause.


> Other threads, such as timer-threads and file-listener threads, are running normally. It seems like only the request comming through the connectors (the AJP12 and HTTP) are hanging. 
>  
> Does anybody recognise these problems? And does anybody have any suggestions about how to fix this? 

see below.

> We have tried to run without Apache and AJP12, but we got the same problem. 
>  
> I could mention that we know that we have mobile clients sending requests to the server and if the server is not responding within a certain time, they will "cut-off" the request. Could it be that tomcat is not "releasing" these requests? 

Could just be that your setup is old and overwhelmed.

> Please, any suggestions would be very apprieciated!

# Examine the servers performance under peak load conditions - determine
if it's actually able to handle the demand.

# Plan an upgrade to some newer hardware.

# Plan an upgrade to a newer, supported version of Tomcat.  Keeping up
to date with releases is not essential, but you should stay reasonably
current if you are able.

p

> Thanks in advance! 
>  
> Marko Krejic
> 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org