Sorry, I thought you had a socket write error. Looks like a read error.
-----Original Message----- From: Derrick Koes [mailto:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]