RE: FW: challenging JK connector problem: java.net.SocketException
Let me pose this question: are these messages resulting in reproducable problems? We see these stack traces all the time, but there is no associated problem. I've chalked it up to people clicking refresh and aborting the connection at the right moment because we have no problems associated with the messages. My favorite is the error messages from jk2 that are labeled Recoverable. Why bother logging them as errors if they are recoverable and have no impact. Byron -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 12:02 PM To: Tomcat Users List; [EMAIL PROTECTED] Subject: Re: FW: challenging JK connector problem: java.net.SocketException hi Patrick, i've just tried your suggestion and unfortunately i still get the java.net.SocketExceptions. i installed Tomcat 5.0.25, upgraded my JDK to 1.4.2_07, reinstalled the JK connector (setupJK204.exe). the only real difference it seems is that i'm using Windows XP. how do you install your JK connector? can you show me the contents of your workers2.properties file? here is my workers2.properties: #Look at #http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebcom.ht ml #for parameter description [shm:] info=Scoreboard. Required for reconfiguration and status with multiprocess servers file=C:\jakarta-tomcat-5.0.25\temp\jk2.shm size=1048576 [channel.socket:localhost:8009] info=Ajp13 forwarding over socket tomcatId=localhost:8009 # Map webapps to the Web server uri space [uri:/jsp-examples/*] [uri:/myapp/*] [uri:/servlets-examples/*] maybe there are some differences between my workers file and yours? at this point i'll try anything :) but since you're on unix, your JK connector is most likely not using isapi_redirector2.dll. so maybe there's implementation differences between the unix JK and windows JK... thanks in advance, woodchuck --- [EMAIL PROTECTED] wrote: -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: February 22, 2005 5:20 PM To: [EMAIL PROTECTED] Subject: RE: challenging JK connector problem: java.net.SocketException hello Patrick! thank you for your help, i really appreciate it as i'm at a total loss at the bizarness of the problem (works through Tomcat, but not when going through IIS/JK). i didn't have time to try out your suggestion just yet, but i definitely will. i just wanted to confirm however, because my Tomcat is an old version 4.1.24, did you mean downgrade my current JDK to one that was current at the time 4.1.24 was current? (ie. use the JDK of the same time period?) I think it would be best to upgrade your version of tomcat to 5.0+ and to use the recommended jdk. I am using tomcat 5.0.28 with jdk 1.4.2_07 on the operating system Linux Enterprise 3.0. or did you mean upgrade my JDK to the latest current release which i believe is 1.5 or something. i am currently using JDK 1.4.1_02. best regards, woodchuck --- [EMAIL PROTECTED] wrote: Hi : This is most likely an issue with the version of JDK that is deployed on your machine. Try using a newer version of the JDK which is comaptible with the version of tomcat that is deployed on your machine. Patrick King Patrick King BSc.(Hon.) Geophysics Senior Systems Scientist Canada Centre For Remote Sensing 615 Booth St. Room 650 Ottawa, Ontario K1A0E9 Phone: 613-947-0463 E-mail : [EMAIL PROTECTED] -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: February 22, 2005 2:15 PM To: tomcat; struts Subject: challenging JK connector problem: java.net.SocketException hihi all, i have installed the JK connector (setupJK204.exe) with my IIS 5.1 and Tomcat 4.1.24. everything is working fine, except that i'm noticing in the Tomcat console display i see the following exceptions at run-time: java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) snip. and java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407
RE: FW: challenging JK connector problem: java.net.SocketException
hello Byron! as far as i can tell, these java.net.SocketExceptions are not causing any real harm in our application. the application seems to work fine. however, these exceptions are unpredictable in that i cannot generate them at will with absolute certainty. sometimes they appear, and sometimes not (when doing the same thing(s) over and over in the app). i've never seen the Recoverable error message though... woodchuck --- Guernsey, Byron (GE Consumer Industrial) [EMAIL PROTECTED] wrote: Let me pose this question: are these messages resulting in reproducable problems? We see these stack traces all the time, but there is no associated problem. I've chalked it up to people clicking refresh and aborting the connection at the right moment because we have no problems associated with the messages. My favorite is the error messages from jk2 that are labeled Recoverable. Why bother logging them as errors if they are recoverable and have no impact. Byron -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 12:02 PM To: Tomcat Users List; [EMAIL PROTECTED] Subject: Re: FW: challenging JK connector problem: java.net.SocketException hi Patrick, i've just tried your suggestion and unfortunately i still get the java.net.SocketExceptions. i installed Tomcat 5.0.25, upgraded my JDK to 1.4.2_07, reinstalled the JK connector (setupJK204.exe). the only real difference it seems is that i'm using Windows XP. how do you install your JK connector? can you show me the contents of your workers2.properties file? here is my workers2.properties: #Look at #http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebcom.ht ml #for parameter description [shm:] info=Scoreboard. Required for reconfiguration and status with multiprocess servers file=C:\jakarta-tomcat-5.0.25\temp\jk2.shm size=1048576 [channel.socket:localhost:8009] info=Ajp13 forwarding over socket tomcatId=localhost:8009 # Map webapps to the Web server uri space [uri:/jsp-examples/*] [uri:/myapp/*] [uri:/servlets-examples/*] maybe there are some differences between my workers file and yours? at this point i'll try anything :) but since you're on unix, your JK connector is most likely not using isapi_redirector2.dll. so maybe there's implementation differences between the unix JK and windows JK... thanks in advance, woodchuck --- [EMAIL PROTECTED] wrote: -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: February 22, 2005 5:20 PM To: [EMAIL PROTECTED] Subject: RE: challenging JK connector problem: java.net.SocketException hello Patrick! thank you for your help, i really appreciate it as i'm at a total loss at the bizarness of the problem (works through Tomcat, but not when going through IIS/JK). i didn't have time to try out your suggestion just yet, but i definitely will. i just wanted to confirm however, because my Tomcat is an old version 4.1.24, did you mean downgrade my current JDK to one that was current at the time 4.1.24 was current? (ie. use the JDK of the same time period?) I think it would be best to upgrade your version of tomcat to 5.0+ and to use the recommended jdk. I am using tomcat 5.0.28 with jdk 1.4.2_07 on the operating system Linux Enterprise 3.0. or did you mean upgrade my JDK to the latest current release which i believe is 1.5 or something. i am currently using JDK 1.4.1_02. best regards, woodchuck --- [EMAIL PROTECTED] wrote: Hi : This is most likely an issue with the version of JDK that is deployed on your machine. Try using a newer version of the JDK which is comaptible with the version of tomcat that is deployed on your machine. Patrick King Patrick King BSc.(Hon.) Geophysics Senior Systems Scientist Canada Centre For Remote Sensing 615 Booth St. Room 650 Ottawa, Ontario K1A0E9 Phone: 613-947-0463 E-mail : [EMAIL PROTECTED] -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: February 22, 2005 2:15 PM To: tomcat; struts Subject: challenging JK connector problem: java.net.SocketException hihi all, i have installed the JK connector (setupJK204.exe) with my IIS 5.1 and Tomcat 4.1.24. everything is working fine, except that i'm noticing in the Tomcat console display i see the following exceptions at run-time: java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222
FW: challenging JK connector problem: java.net.SocketException
-Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: February 22, 2005 5:20 PM To: [EMAIL PROTECTED] Subject: RE: challenging JK connector problem: java.net.SocketException hello Patrick! thank you for your help, i really appreciate it as i'm at a total loss at the bizarness of the problem (works through Tomcat, but not when going through IIS/JK). i didn't have time to try out your suggestion just yet, but i definitely will. i just wanted to confirm however, because my Tomcat is an old version 4.1.24, did you mean downgrade my current JDK to one that was current at the time 4.1.24 was current? (ie. use the JDK of the same time period?) I think it would be best to upgrade your version of tomcat to 5.0+ and to use the recommended jdk. I am using tomcat 5.0.28 with jdk 1.4.2_07 on the operating system Linux Enterprise 3.0. or did you mean upgrade my JDK to the latest current release which i believe is 1.5 or something. i am currently using JDK 1.4.1_02. best regards, woodchuck --- [EMAIL PROTECTED] wrote: Hi : This is most likely an issue with the version of JDK that is deployed on your machine. Try using a newer version of the JDK which is comaptible with the version of tomcat that is deployed on your machine. Patrick King Patrick King BSc.(Hon.) Geophysics Senior Systems Scientist Canada Centre For Remote Sensing 615 Booth St. Room 650 Ottawa, Ontario K1A0E9 Phone: 613-947-0463 E-mail : [EMAIL PROTECTED] -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: February 22, 2005 2:15 PM To: tomcat; struts Subject: challenging JK connector problem: java.net.SocketException hihi all, i have installed the JK connector (setupJK204.exe) with my IIS 5.1 and Tomcat 4.1.24. everything is working fine, except that i'm noticing in the Tomcat console display i see the following exceptions at run-time: java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) snip. and java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) snip in particular these exceptions are coming up when i use my app's search functionality the weird part is that the exceptions only occur when i access my web site through IIS (ie. via JK connector). i *don't* get any exceptions at all when accessing Tomcat directly by specifying port 8080 in my URL. these exceptions are causing weird/incorrect app behaviour in the search functionality as well, so it's not just harmless exception logs being generated. if i use my application by connecting to Tomcat directly (port 8080), the search functionality works perfectly and there's no errors at all. i have looked at my code and cannot see what i could be doing that may cause such errors to happen in the JK connector. has anyone any suggestions on how to go about debugging this? or has come across this before and found a solution? in my search page, i am using logic:present and logic:empty struts tags to detect if my collection (of search results) object is null or not, and if not, is it an empty collection or not respectively. is this a known bug/issue perhaps with some struts tags being used through JK connector? why is connection reset by peer happening? doesn't this mean the request/form being submitted is suddenly cut off? any help is appreciated. please and thanks, woodchuck __ Do you Yahoo!? All your favorites on one personal page - Try My Yahoo! http://my.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail
Re: FW: challenging JK connector problem: java.net.SocketException
hi Patrick, i've just tried your suggestion and unfortunately i still get the java.net.SocketExceptions. i installed Tomcat 5.0.25, upgraded my JDK to 1.4.2_07, reinstalled the JK connector (setupJK204.exe). the only real difference it seems is that i'm using Windows XP. how do you install your JK connector? can you show me the contents of your workers2.properties file? here is my workers2.properties: #Look at #http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebcom.html #for parameter description [shm:] info=Scoreboard. Required for reconfiguration and status with multiprocess servers file=C:\jakarta-tomcat-5.0.25\temp\jk2.shm size=1048576 [channel.socket:localhost:8009] info=Ajp13 forwarding over socket tomcatId=localhost:8009 # Map webapps to the Web server uri space [uri:/jsp-examples/*] [uri:/myapp/*] [uri:/servlets-examples/*] maybe there are some differences between my workers file and yours? at this point i'll try anything :) but since you're on unix, your JK connector is most likely not using isapi_redirector2.dll. so maybe there's implementation differences between the unix JK and windows JK... thanks in advance, woodchuck --- [EMAIL PROTECTED] wrote: -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: February 22, 2005 5:20 PM To: [EMAIL PROTECTED] Subject: RE: challenging JK connector problem: java.net.SocketException hello Patrick! thank you for your help, i really appreciate it as i'm at a total loss at the bizarness of the problem (works through Tomcat, but not when going through IIS/JK). i didn't have time to try out your suggestion just yet, but i definitely will. i just wanted to confirm however, because my Tomcat is an old version 4.1.24, did you mean downgrade my current JDK to one that was current at the time 4.1.24 was current? (ie. use the JDK of the same time period?) I think it would be best to upgrade your version of tomcat to 5.0+ and to use the recommended jdk. I am using tomcat 5.0.28 with jdk 1.4.2_07 on the operating system Linux Enterprise 3.0. or did you mean upgrade my JDK to the latest current release which i believe is 1.5 or something. i am currently using JDK 1.4.1_02. best regards, woodchuck --- [EMAIL PROTECTED] wrote: Hi : This is most likely an issue with the version of JDK that is deployed on your machine. Try using a newer version of the JDK which is comaptible with the version of tomcat that is deployed on your machine. Patrick King Patrick King BSc.(Hon.) Geophysics Senior Systems Scientist Canada Centre For Remote Sensing 615 Booth St. Room 650 Ottawa, Ontario K1A0E9 Phone: 613-947-0463 E-mail : [EMAIL PROTECTED] -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: February 22, 2005 2:15 PM To: tomcat; struts Subject: challenging JK connector problem: java.net.SocketException hihi all, i have installed the JK connector (setupJK204.exe) with my IIS 5.1 and Tomcat 4.1.24. everything is working fine, except that i'm noticing in the Tomcat console display i see the following exceptions at run-time: java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) snip. and java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) snip in particular these exceptions are coming up when i use my app's search functionality the weird part is that the exceptions only occur when i access my web site through IIS (ie. via JK connector). i *don't* get any exceptions at all when accessing Tomcat directly by specifying port 8080 in my URL. these exceptions are causing weird/incorrect app behaviour in the search functionality
challenging JK connector problem: java.net.SocketException
hihi all, i have installed the JK connector (setupJK204.exe) with my IIS 5.1 and Tomcat 4.1.24. everything is working fine, except that i'm noticing in the Tomcat console display i see the following exceptions at run-time: java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) snip. and java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) snip in particular these exceptions are coming up when i use my app's search functionality the weird part is that the exceptions only occur when i access my web site through IIS (ie. via JK connector). i *don't* get any exceptions at all when accessing Tomcat directly by specifying port 8080 in my URL. these exceptions are causing weird/incorrect app behaviour in the search functionality as well, so it's not just harmless exception logs being generated. if i use my application by connecting to Tomcat directly (port 8080), the search functionality works perfectly and there's no errors at all. i have looked at my code and cannot see what i could be doing that may cause such errors to happen in the JK connector. has anyone any suggestions on how to go about debugging this? or has come across this before and found a solution? in my search page, i am using logic:present and logic:empty struts tags to detect if my collection (of search results) object is null or not, and if not, is it an empty collection or not respectively. is this a known bug/issue perhaps with some struts tags being used through JK connector? why is connection reset by peer happening? doesn't this mean the request/form being submitted is suddenly cut off? any help is appreciated. please and thanks, woodchuck __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: challenging JK connector problem: java.net.SocketException
Hi : This is most likely an issue with the version of JDK that is deployed on your machine. Try using a newer version of the JDK which is comaptible with the version of tomcat that is deployed on your machine. Patrick King Patrick King BSc.(Hon.) Geophysics Senior Systems Scientist Canada Centre For Remote Sensing 615 Booth St. Room 650 Ottawa, Ontario K1A0E9 Phone: 613-947-0463 E-mail : [EMAIL PROTECTED] -Original Message- From: Woodchuck [mailto:[EMAIL PROTECTED] Sent: February 22, 2005 2:15 PM To: tomcat; struts Subject: challenging JK connector problem: java.net.SocketException hihi all, i have installed the JK connector (setupJK204.exe) with my IIS 5.1 and Tomcat 4.1.24. everything is working fine, except that i'm noticing in the Tomcat console display i see the following exceptions at run-time: java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) snip. and java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:372) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) snip in particular these exceptions are coming up when i use my app's search functionality the weird part is that the exceptions only occur when i access my web site through IIS (ie. via JK connector). i *don't* get any exceptions at all when accessing Tomcat directly by specifying port 8080 in my URL. these exceptions are causing weird/incorrect app behaviour in the search functionality as well, so it's not just harmless exception logs being generated. if i use my application by connecting to Tomcat directly (port 8080), the search functionality works perfectly and there's no errors at all. i have looked at my code and cannot see what i could be doing that may cause such errors to happen in the JK connector. has anyone any suggestions on how to go about debugging this? or has come across this before and found a solution? in my search page, i am using logic:present and logic:empty struts tags to detect if my collection (of search results) object is null or not, and if not, is it an empty collection or not respectively. is this a known bug/issue perhaps with some struts tags being used through JK connector? why is connection reset by peer happening? doesn't this mean the request/form being submitted is suddenly cut off? any help is appreciated. please and thanks, woodchuck __ Do you Yahoo!? All your favorites on one personal page - Try My Yahoo! http://my.yahoo.com - 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]
