tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derrick Koes" <Derrick_K...@skillsoft.com>
Subject RE: Socket Exception - Heavy load
Date Fri, 07 Jan 2005 20:07:36 GMT
 

maxThreads isn't a valid connector attribute, right?

Did you mean maxProcessors?

http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/ajp.html

The maximum number of processors allowed. This should be set to a value that is greater than
or equal to the maximum number of concurrent connections the remote web server can open to
Tomcat simultaneously. For example, if the web server is Apache 1.x or 2.x Tomcat's maxProcessors
should be set to the value of Apache's maxClients directive.

A maxProcessors value of zero (0) signifies that the number of processors is unlimited. If
not specified, this atttribute defaults to 20.


Try setting to 0 if you have many concurrent active connections.




-----Original Message-----
From: Derrick Koes [mailto:Derrick_Koes@skillsoft.com] 
Sent: Friday, January 07, 2005 2:58 PM
To: Tomcat Users List
Subject: RE: Socket Exception - Heavy load

 
Do you see the problem when 

# worker.worker1.cachesize=200
# worker.worker1.cache_timeout=60
# worker.worker1.socket_keepalive=1
# worker.worker1.reclycle_timeout=60
# worker.worker1.retries=5

That is, defaults used for all these properties.

BTW, you don't need an lbfactor unless this is actually a load balanced worker.
Also, what do your JK logs say with debugging turned up around the time of the error?  You
have to set this in the registry for JK.


-----Original Message-----
From: shyam [mailto:gshyam_reddy@hotmail.com]
Sent: Friday, January 07, 2005 2:49 PM
To: 'Tomcat Users List'
Subject: RE: Socket Exception - Heavy load

I am including my workers.properties here # Define 1 real worker using ajp13
  worker.list=worker1
  # Set properties for worker1 (ajp13)
  worker.worker1.type=ajp13
  worker.worker1.host=localhost
  worker.worker1.port=8009
  worker.worker1.lbfactor=50
  worker.worker1.cachesize=200
  worker.worker1.cache_timeout=60
  worker.worker1.socket_keepalive=1
  worker.worker1.reclycle_timeout=60
  worker.worker1.retries=5

this the server.xml configuration of tomcat
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" 
               enableLookups="false" redirectPort="8443" debug="0"
               protocol="AJP/1.3" maxThreads="1000" />

thanks
shyam


-----Original Message-----
From: Derrick Koes [mailto:Derrick_Koes@skillsoft.com]
Sent: Friday, January 07, 2005 2:43 PM
To: Tomcat Developers List; Tomcat Users List
Subject: RE: Socket Exception - Heavy load


What is your wait_timeout set to? 


<ContactInfo>
  <Name>Derrick Koes</Name>
  <Title>Senior Software Engineer</Title>
  <Company name="SkillSoft"
    url="http://www.skillsoft.com"/>
  <AIM>codeauthor2001</AIM>
  <Email>Derrick_Koes@skillsoft.com</Email>
  <Phone>(603) 821-3260</Phone>
  <Cell>(603) 305-1753</Cell>
  <Fax/>
  <Quote attributedTo="Yoda">No, try not, do
    or do not, there is no try.</Quote>
</ContactInfo>
-----Original Message-----
From: Derrick Koes [mailto:Derrick_Koes@skillsoft.com]
Sent: Friday, January 07, 2005 2:38 PM
To: Tomcat Developers List; Tomcat Users List
Subject: RE: Socket Exception - Heavy load

 
Sorry, I thought you had a socket write error.  Looks like a read error.



-----Original Message-----
From: Derrick Koes [mailto:Derrick_Koes@skillsoft.com]
Sent: Friday, January 07, 2005 2:35 PM
To: Tomcat Users List
Cc: Tomcat Developers List
Subject: RE: Socket Exception - Heavy load

 

Windows is notorious for holding the socket binding for some time after the close is done.
 I expected that you would see a BindException, not a SocketException.

This exception is thrown if a socket cannot be created and bound to the requested port.

However, your error looks like the receiver dropped the connection.
If the OutputStream was closed after you finished sending (before you started receiving),
that's the cause of your problem, since closing the OutputStream also closes the socket.

In any event it's the client that is closing the socket connection.

BTW, 1.2.8 refers to a JK version not JK2 unless there is some really old version of JK2 of
which I'm not aware.

Perhaps Mladen Turk (JK expert) can help.


-----Original Message-----
From: shyam [mailto:gshyam_reddy@hotmail.com]
Sent: Friday, January 07, 2005 2:17 PM
To: 'Tomcat Users List'
Subject: RE: Socket Exception - Heavy load

Hi Mark,
Thanks. I would remember this .
Thanks
shyam

-----Original Message-----
From: Mark Thomas [mailto:markt@apache.org]
Sent: Friday, January 07, 2005 2:10 PM
To: Tomcat Users List
Subject: Re: Socket Exception - Heavy load

Please do not hijack another message thread.

If you wish to post to the list create a new message and send it. DO NOT

reply to a list message and change the subject. Thread aware mail clients still recognise
this as a reply and do not show it as a new message.

Mark
tomcat-user-owner@jakarta.apache.org


shyam wrote:
> Hi All,
> 
> I am doing some performance tests. Under heavy load I get socket 
> exceptions in my tomcat logs
> 
> SEVERE: Error, processing connection
> java.net.SocketException: Software caused connection abort: recv
failed
> 	at java.net.SocketInputStream.socketRead0(Native Method)
> 	at java.net.SocketInputStream.read(Unknown Source)
> 	at java.io.BufferedInputStream.fill(Unknown Source)
> 	at java.io.BufferedInputStream.read1(Unknown Source)
> 	at java.io.BufferedInputStream.read(Unknown Source)
> 	at
> org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:556)
> 	at
> org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:494)
> 	at
>
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:
> 614)
> 	at
> org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:807)
> 	at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
> java:644)
> 	at java.lang.Thread.run(Unknown Source)
> 
> I guess it has something to do with jk2 and the sockets. It would be 
> helpful if someone can explain this and why it is happening?
> My configuration is
> Apache 2.0.52
> Tomcat 5.0.29
> Jk2 - 1.2.8
> 
> Thanks
> shyam
> 
> ---------------------------------------------------------------------
> 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


---------------------------------------------------------------------
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-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-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


---------------------------------------------------------------------
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





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


Mime
View raw message