Re: tomcat 4.1.18/24 unstable (UPDATE)

[joseph lam <jo...@quotepower.com>]

I just found out what caused the 'ESTABLISHED' connection piling up 
problem. It was due to a javascript form.submit() triggered by pressing 
'Enter' key which causes IE to double submit the form. What it does so 
it will first submit the form, then quickly send a reset and submit it 
again. That seems to confuse Tomcat. After fixing the Javascript the 
problem is largely gone.

Joseph

joseph lam wrote:

> I also had the same problem with both 4.1.18 and 24. Now I resort to 
> setting a high maxProcessor (e.g. 800) and restart the tomcat once the 
> connections are reaching that. I also found that those 'ESTABLISHED' 
> connections would stay forever eating up sockets and tomcat 
> connectors. I've also tried to tune the ipv4 kernel settings for 
> example to shorten the keep alive timeout but no luck.
>
> I'm using Redhat 7.3 and Sun JDK 1.4.1_02.
>
> Joseph
>
> Eric Roberts wrote:
>
>> We currently have secure web services deployed within tomcat 4.1.18
>> using axis.  We have 4 or 5 backend information providers submitting
>> information to the web service every 5 minutes.  Every so often I can
>> run a 'netstat -an | grep 8443' and see roughly 100+ connections with
>> the ESTABLISHED status.  It seems as though the connections are hanging
>> from the tomcat end.  Has anyone else experienced this? 
>> ( the limit of connections in tomcat is set to 100, time out is 20000 in
>> server.xml )
>>
>> Thanks in advance
>>
>>  
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org