tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pid <...@pidster.com>
Subject Re: R: Re: intermittent SocketException on startup tomcat 5.5.28 and under JBOSS 4.2.3GA
Date Sat, 05 Jun 2010 20:00:40 GMT
On 05/06/2010 20:56, agonat@libero.it wrote:
> Thanks for replay.
> I'm sorry 
> I have missed e-mail regard server .xml with romment removed.
> so I attached this file.
> 
> 
> regard <Context path="" docBase="SIT/"/> i think that a mistake the correct 
> form is in the file.
> "SIT" is name of my application. 

So in the file you attached, you have:

 <Context path="" docBase="/SIT" />

Is the SIT application at:

 path/to/tomcat/webapps/SIT

or somewhere else?


p


> I don't able to match timestamp of error whith a request because i don't know 
> how to trace all request in tomcat conaitner. How can do it?
> I have essentially only catalina_log (with error)  and standard_out_log (in 
> which i have application "SIT" stdout message).
> Best regards
> Agostino
> 
>> ----Messaggio originale----
>> Da: pid@pidster.com
>> Data: 05/06/2010 21.26
>> A: "Tomcat Users List"<users@tomcat.apache.org>
>> Ogg: Re: R: Re: R: RE: Re: intermittent SocketException on startup tomcat 
> 5.5.28 and under JBOSS 4.2.3GA
>>
>> On 05/06/2010 14:41, agonat@libero.it wrote:
>>> Thanks 
>>>
>>> The question started in 
>>> http://mail-archives.apache.org/mod_mbox/tomcat-users/201005.mbox/thread?
> 3    
>>> on same thread.
>>>
>>> Now i have reduce the number of user (about 50 user simultanely) on a   
>>> win2003 ED quad processor with 8GB bram (I have tomcat 5.5.28, jdk.1.6.16, 
> IIS 
>>> (with certificate instaled) on port 80 that redirect  request from port 80 
> to 
>>> 8080 tomcat connector   server. Besides https request are directly managed 
> from 
>>> second connector, on port 443 of tomcat.)
>>>
>>> So  the error referred, sometime occours. In particular i have noted that 
> this 
>>> error rise when a lot user make  login in the application (  in a few 
> second).
>>> Probably  this may be depend from a lot tcp/ip connection, but, this 
> using 
>>> netstat -na not appear.
>>> May be i must increase the number on maxTcpConnection on win2003 server 
> and/or 
>>> reduce tcpDelay.
>>> Please give me a help to resolve the problem.
>>> What tool i can use for investigate who cause socket close.
>>>
>>> The part of default server.xml of tomcat  that i have change(2 connector 
>>> configuration an docbase) is :
>>
>> I guess you missed the bit about "comments removed".
>> Why not backup that file, and then create a server.xml with all of the
>> comments removed?
>>
>>> .......
>>>
>>>     <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
>>>     <Connector
>>> port="8080"    maxHttpHeaderSize="8192"
>>>                maxThreads="350" minSpareThreads="50" maxSpareThreads="100"
>>>                enableLookups="false" redirectPort="443" acceptCount="100"
>>>                connectionTimeout="20000" disableUploadTimeout="true" />
>>>
>>> 	
>>> 	<!-- Note : To disable connection timeouts, set connectionTimeout value
>>>      to 0 -->
>>> 	
>>> 	<!-- Note : To use gzip compression you could set the following properties

> :
>>> 	
>>> 			   compression="on" 
>>> 			   compressionMinSize="2048" 
>>> 			   noCompressionUserAgents="gozilla, traviata" 
>>> 			   compressableMimeType="text/html,text/xml"
>>> 	-->
>>>
>>>     <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
>>>     <!--
>>>     <Connector port="8443" maxHttpHeaderSize="8192"
>>>                maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
>>>                enableLookups="false" disableUploadTimeout="true"
>>>                acceptCount="100" scheme="https" secure="true"
>>>                clientAuth="false" sslProtocol="TLS" />
>>>     -->
>>> 	
>>>     <Connector port="443" maxHttpHeaderSize="10240" 
>>>                maxThreads="150" minSpareThreads="25" maxSpareThreads="
> 100" 
>>>                enableLookups="false" disableUploadTimeout="true"
>>>                acceptCount="100" scheme="https" secure="true"
>>>                clientAuth="false" sslProtocol="TLS" 
>>> 			   keystoreFile="C:\CertificatiHTTPS\aaa.pfx"
>>> 			   keystorePass="bbbb"
>>> 			   keystoreType="PKCS12"
>>> 			   />
>>> 	
>>> 	
>>>     <!-- Define an AJP 1.3 Connector on port 8009 -->
>>>     <Connector port="8009" 
>>>                enableLookups="false" redirectPort="443" protocol="AJP/1.3" 
> />
>>>
>>>     <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
>>>     <!-- See proxy documentation for more information about using this. --
>>
>>>     <!--
>>>
>>> ........
>>>
>>>      <!-- Define the default virtual host 
>>>            Note: XML Schema validation will not work with Xerces 2.2.
>>>        -->
>>>       <Host name="localhost" appBase="webapps"
>>>        unpackWARs="true" autoDeploy="true"
>>>        xmlValidation="false" xmlNamespaceAware="false">
>>>
>>> 	
>>> 		<Context path="" docBase="SIT/"/>
>>
>> Is the above accurate, or is the extra slash after SIT an error?
>>
>> If it is accurate, it's wrong and will also cause double deployment -
>> once as "/SIT/" and once as "/".
>>
>>
>> Are you able to match timestamps of the Socket close exception to a
>> particular request, and is there a matching request in the log?
>>
>>
>> p
>>
>> 	
>>>         <!-- Defines a cluster for this node,
>>>              By defining this element, means that every manager will be 
>>> changed.
>>>              So when running a cluster, only make sure that you have 
> webapps 
>>> in there
>>>              that need to be clustered and remove the other ones.
>>>              A cluster has the following parameters:
>>> -->
>>> ........
>>>
>>>
>>>
>>>
>>>> ----Messaggio originale----
>>>> Da: rainer.jung@kippdata.de
>>>> Data: 05/06/2010 11.09
>>>> A: "Tomcat Users List"<users@tomcat.apache.org>
>>>> Ogg: Re: R: RE: Re: intermittent SocketException on startup tomcat 5.5.28

> and 
>>> under JBOSS 4.2.3GA
>>>>
>>>> On 05.06.2010 09:23, Pid * wrote:
>>>>> On 5 Jun 2010, at 04:33, "agonat@libero.it"<agonat@libero.it> 
wrote:
>>>>>
>>>>>> Hi
>>>>>>     I m very tired because the intermittent socket close exception
>>>>>> reappear.
>>>>>>
>>>>>>     We now use tomcat 5.5.28 on win2003 ED SO and jdk 1.6.16.
>>>>>>     The error that occours is:
>>>>>>
>>>>>>     4-giu-2010 7.48.35
>>>>
>>>> Date and Time in a bit strange format: 4th of June 2010, 07:48:35.
>>>>
>>>> Rainer
>>>>
>>>>> What is the above? It doesn't look familiar to me.
>>>>>
>>>>> Can you refresh our memories and please post the current server.xml
>>>>> (comments removed)?
>>>>>
>>>>>
>>>>> p
>>>>>
>>>>>> org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket
>>>>>> GRAVE: Endpoint ServerSocket
>>>>>> [addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
>>>>>> ignored exception: java.net.SocketException: socket closed
>>>>>> java.net.SocketException: socket closed
>>>>>>     at java.net.PlainSocketImpl.socketAccept(Native Method)
>>>>>>     at java.net.PlainSocketImpl.accept(Unknown Source)
>>>>>>     at java.net.ServerSocket.implAccept(Unknown Source)
>>>>>>     at java.net.ServerSocket.accept(Unknown Source)
>>>>>>     at
>>>>>> org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket
>>>>>> (DefaultServerSocketFactory.java:61)
>>>>>>     at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket
>>>>>> (PoolTcpEndpoint.
>>>>>> java:408)
>>>>>>     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
>>>>>> (LeaderFollowerWorkerThread.java:71)
>>>>>>     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
>>>>>> (ThreadPool.
>>>>>> java:689)
>>>>>>     at java.lang.Thread.run(Unknown Source)
>>>>>> 4-giu-2010 7.48.56 org.apache.tomcat.util.net.PoolTcpEndpoint
>>>>>> acceptSocket
>>>>>> AVVERTENZA: Reinitializing ServerSocket
>>>>>> 4-giu-2010 8.04.39 org.apache.tomcat.util.net.PoolTcpEndpoint
>>>>>> acceptSocket
>>>>>> GRAVE: Endpoint ServerSocket
>>>>>> [addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
>>>>>> ignored exception: java.net.SocketException: socket closed
>>>>>> java.net.SocketException: socket closed
>>>>>>     at java.net.PlainSocketImpl.socketAccept(Native Method)
>>>>>>     at java.net.PlainSocketImpl.accept(Unknown Source)
>>>>>>     at java.net.ServerSocket.implAccept(Unknown Source)
>>>>>>     at java.net.ServerSocket.accept(Unknown Source)
>>>>>>     at
>>>>>> org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket
>>>>>> (DefaultServerSocketFactory.java:61)
>>>>>>     at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket
>>>>>> (PoolTcpEndpoint.
>>>>>> java:408)
>>>>>>     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
>>>>>> (LeaderFollowerWorkerThread.java:71)
>>>>>>     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
>>>>>> (ThreadPool.
>>>>>> java:689)
>>>>>>     at java.lang.Thread.run(Unknown Source)
>>>>>> 4-giu-2010 8.05.00 org.apache.tomcat.util.net.PoolTcpEndpoint
>>>>>> acceptSocket
>>>>>> AVVERTENZA: Reinitializing ServerSocket
>>>>>> 4-giu-2010 8.05.00 org.apache.tomcat.util.net.PoolTcpEndpoint
>>>>>> acceptSocket
>>>>>> GRAVE: Endpoint ServerSocket
>>>>>> [addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
>>>>>> ignored exception: java.net.SocketException: socket closed
>>>>>> java.net.SocketException: socket closed
>>>>>>     at java.net.PlainSocketImpl.socketAccept(Native Method)
>>>>>>     at java.net.PlainSocketImpl.accept(Unknown Source)
>>>>>>     at java.net.ServerSocket.implAccept(Unknown Source)
>>>>>>     at java.net.ServerSocket.accept(Unknown Source)
>>>>>>     at
>>>>>> org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket
>>>>>> (DefaultServerSocketFactory.java:61)
>>>>>>     at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket
>>>>>> (PoolTcpEndpoint.
>>>>>> java:408)
>>>>>>     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt
>>>>>> (LeaderFollowerWorkerThread.java:71)
>>>>>>     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
>>>>>> (ThreadPool.
>>>>>> java:689)
>>>>>>     at java.lang.Thread.run(Unknown Source)
>>>>>> 4-giu-2010 8.05.21 org.apache.tomcat.util.net.PoolTcpEndpoint
>>>>>> acceptSocket
>>>>>> AVVERTENZA: Reinitializing ServerSocket
>>>>>> 4-giu-2010 8.06.55 org.apache.tomcat.util.net.PoolTcpEndpoint
>>>>>> acceptSocket
>>>>>> GRAVE: Endpoint ServerSocket
>>>>>> [addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
>>>>>> ignored exception: java.net.SocketException: socket closed
>>>>>> java.net.SocketException: socket closed
>>>>>>     at java.net.PlainSocketImpl.socketAccept(Native Method) .....
>>>>>>
>>>>>>     This error slow down the application.
>>>>>>
>>>>>>     we don't have  firewall, pool of tcp connection seem correct,
the
>>>>>> processor
>>>>>> and memory usage are normal (10% CPU and 50% RAM).
>>>>>>
>>>>>>
>>>>>> How can  i investigte who cuse the problem?  Jconsole observe memory
>>>>>> but seem
>>>>>> not tcp connection.
>>>>>>     How can i understand why i have close socket?
>>>>>>     whath are flakey router error?
>>>>>>     How can i understand if i have saturate the connection on SO?
>>>>>>
>>>>>>     Thank for all suggest
>>>>>>     Best regards
>>>>>>     Agostino
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> ----Messaggio originale----
>>>>>>> Da: Chuck.Caldarale@unisys.com
>>>>>>> Data: 24/05/2010 15.38
>>>>>>> A: "Tomcat Users List"<users@tomcat.apache.org>, "agonat@libero.it"
>>>>>> <agonat@libero.it>
>>>>>>> Ogg: RE: Re: intermittent SocketException on startup tomcat 5.5.28
>>>>>>> and under
>>>>>> JBOSS 4.2.3GA
>>>>>>>
>>>>>>>> From: agonat@libero.it [mailto:agonat@libero.it]
>>>>>>>> Subject: R: Re: intermittent SocketException on startup tomcat
>>>>>>>> 5.5.28
>>>>>>>> and under JBOSS 4.2.3GA
>>>>>>>>
>>>>>>>> ERROR [org.apache.tomcat.util.net.JIoEndpoint]
>>>>>>>> Socket accept failed
>>>>>>>> java.net.SocketException: socket closed
>>>>>>>
>>>>>>> This isn't really a problem with the Tomcat server - it usually
>>>>>>> means the
>>>>>> client terminated the connection attempt before the socket on the
>>>>>> server end
>>>>>> could be created.  If this is happening persistently, then something
>>>>>> in between
>>>>>> the client and Tomcat (e.g., a firewall or flakey router) is
>>>>>> dropping the
>>>>>> connection before it can be fully established.  There's also a
>>>>>> possibility that
>>>>>> Windows is reaching some resource limit and preventing creation of
>>>>>> the server
>>>>>> end of the connection.
>>>>>>>
>>>>>>> - Chuck
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>
>>
>>
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org



Mime
View raw message