You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Eric Roberts <er...@austin.tacc.utexas.edu> on 2003/05/07 17:53:48 UTC
tomcat 4.1.18 unstable
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
Re: tomcat 4.1.18/24 unstable (UPDATE)
Posted by 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
Re: tomcat 4.1.18 unstable
Posted by joseph lam <jo...@quotepower.com>.
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
Re: tomcat 4.1.18 unstable
Posted by Lajos <la...@galatea.com>.
I had that problem last weekend with my 4.0.6 site (RH 7.2). After
researching the problem, I found that I had a js sniffer script in my
pages that was causing the browers to hang. Once I removed the offending
js file, my site only shows about 30 active connections at a time, which
means they are properly being recycled.
I would check your Axis app and make sure there is nothing that can
cause the connection to stay open.
Regards,
Lajos
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
>
--
Lajos Moczar
----------------------------------------
Open Source Support, Consulting and Training
----------------------------------------
Cocoon Developer's Handbook
(www.amazon.com/exec/obidos/tg/detail/-/0672322579)
_ _____
/ \ /
/___\ /
/ \ /____
http://www.galatea.com -- powered by AzSSL
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Newbie - unable to set default contexct
Posted by Jacob Kjome <ho...@visi.com>.
How do you expect tomcat to read a <Context> entry that is commented
out? Also, you may need to remove the ROOT context directory. That
directory name is treated specially by Tomcat. If present, it serves as
the <Context path="" ...>. You might just want to put the contents of your
context in to the ROOT directory. It will make things easier and avoid
conflicts. You don't even need to define a <Context ...> entry if you do this.
Jake
At 10:01 PM 5/13/2003 +0100, you wrote:
>Folks,
>
>
>
>I have the installed TC 4.1.24 on RedHat 7.2.
>All went well - the Tomcat default page comes up fine.
>
>I need to replace the default page with my own stuff however, so I
>installed my app ("escapism") in the webapps dir and edited server.xml
>thus:
>
><!-- Tomcat Root Context -->
><!--
> <Context path="" docBase="escapism" debug="0"/>
>-->
>
>I restarted TC but the standard TC home page still is displayed when
>accessing "http://localhost:8080/"
>
>
>My understanding is that this should set the default Tomcat page to
>webapps/escapism/index.jsp.
>Is this correct? If not how do I do it?
>
>
>TIA - Adam
>
>
>---
>Outgoing mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.480 / Virus Database: 276 - Release Date: 12/05/2003
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RE: tomcat 4.1.18 unstable
Posted by George Sexton <gs...@mhsoftware.com>.
You haven't provided the barest amount of information to be useful.
What operating system are you using?
What JDK are you using?
-----Original Message-----
From: Eric Roberts [mailto:ericrobe@austin.tacc.utexas.edu]
Sent: Wednesday, May 07, 2003 9:54 AM
To: tomcat-user@jakarta.apache.org
Subject: tomcat 4.1.18 unstable
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
Newbie - unable to set default contexct
Posted by Adam Lipscombe <ad...@cobar.fsbusiness.co.uk>.
Folks,
I have the installed TC 4.1.24 on RedHat 7.2.
All went well - the Tomcat default page comes up fine.
I need to replace the default page with my own stuff however, so I
installed my app ("escapism") in the webapps dir and edited server.xml
thus:
<!-- Tomcat Root Context -->
<!--
<Context path="" docBase="escapism" debug="0"/>
-->
I restarted TC but the standard TC home page still is displayed when
accessing "http://localhost:8080/"
My understanding is that this should set the default Tomcat page to
webapps/escapism/index.jsp.
Is this correct? If not how do I do it?
TIA - Adam
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.480 / Virus Database: 276 - Release Date: 12/05/2003
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org