RE: JK throws java.lang.NumberFormatException when JSP is not found. (trace logging)
Hi Guys, Well I have trace logging on but there do not appear to be errors in the logs. You can clearly see from the timestamps on the logging below that the errors are linked to each other. As soon as I request a JSP that does not exist, e.g I request http://testserver/nosuchjsp.jsp I get the NumberFormatException in Tomcat stdout and I correctly get the standard Tomcat 404 error page. Does this trace logging help anymore? Cheers, Allistair. STDOUT == Dec 16, 2004 2:19:08 PM org.apache.jk.common.HandlerRequest invoke SEVERE: Error decoding request java.lang.NumberFormatException at org.apache.tomcat.util.buf.Ascii.parseInt(Ascii.java:145) at org.apache.tomcat.util.buf.ByteChunk.getInt(ByteChunk.java:491) at org.apache.tomcat.util.buf.MessageBytes.getInt(MessageBytes.java:645) at org.apache.jk.common.HandlerRequest.decodeHeaders(HandlerRequest.java:682) at org.apache.jk.common.HandlerRequest.decodeRequest(HandlerRequest.java:504) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:361) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:745) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:868) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Dec 16, 2004 2:19:08 PM org.apache.jk.common.ChannelSocket processConnection WARNING: processCallbacks status 2 JK === [Thu Dec 16 14:19:08 2004] [2196:2232] [trace] ajp_get_reply::jk_ajp_common.c (1329): enter [Thu Dec 16 14:19:08 2004] [2196:2232] [trace] ajp_connection_tcp_get_message::jk_ajp_common.c (846): enter [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): received from ajp13 pos=0 len=86 max=8192 [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): 04 01 94 00 0E 2F 6E 6F 73 75 63 68 6A 73 70 2E - ./nosuchjsp. [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): 00106A 73 70 00 00 02 00 0C 43 6F 6E 74 65 6E 74 2D - jsp.Content- [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): 002054 79 70 65 00 00 17 74 65 78 74 2F 68 74 6D 6C - Type...text/html [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): 00303B 63 68 61 72 73 65 74 3D 75 74 66 2D 38 00 00 - ;charset=utf-8.. [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): 00400E 43 6F 6E 74 65 6E 74 2D 4C 65 6E 67 74 68 00 - .Content-Length. [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): 005000 03 39 39 32 00 6D 69 6C 79 3A 54 61 68 6F 6D - ..992.mily:Tahom [Thu Dec 16 14:19:08 2004] [2196:2232] [trace] ajp_connection_tcp_get_message::jk_ajp_common.c (935): exit [Thu Dec 16 14:19:08 2004] [2196:2232] [trace] ajp_process_callback::jk_ajp_common.c (1220): enter [Thu Dec 16 14:19:08 2004] [2196:2232] [trace] ajp_unmarshal_response::jk_ajp_common.c (522): enter [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_unmarshal_response::jk_ajp_common.c (538): status = 404 [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_unmarshal_response::jk_ajp_common.c (544): Number of headers is = 2 [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_unmarshal_response::jk_ajp_common.c (599): Header[0] [Content-Type] = [text/html;charset=utf-8] [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_unmarshal_response::jk_ajp_common.c (599): Header[1] [Content-Length] = [992] [Thu Dec 16 14:19:08 2004] [2196:2232] [trace] ajp_unmarshal_response::jk_ajp_common.c (606): exit [Thu Dec 16 14:19:08 2004] [2196:2232] [trace] start_response::jk_isapi_plugin.c (385): enter [Thu Dec 16 14:19:08 2004] [2196:2232] [trace] start_response::jk_isapi_plugin.c (451): exit [Thu Dec 16 14:19:08 2004] [2196:2232] [trace] ajp_connection_tcp_get_message::jk_ajp_common.c (846): enter [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): received from ajp13 pos=0 len=996 max=8192 [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): 03 03 E0 3C 68 74 6D 6C 3E 3C 68 65 61 64 3E 3C - ...htmlhead [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): 001074 69 74 6C 65 3E 41 70 61 63 68 65 20 54 6F 6D - titleApache.Tom [Thu Dec 16 14:19:08 2004] [2196:2232] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (930): 002063 61 74 2F 35 2E 35 2E 35 20 2D 20 45 72 72 6F - cat/5.5.5.-.Erro [Thu Dec 16 14:19:08 2004] [2196:2232] [debug]
Re: JK throws java.lang.NumberFormatException when JSP is not found. (trace logging)
- Original Message - From: Allistair Crossley [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Thursday, December 16, 2004 6:22 AM Subject: RE: JK throws java.lang.NumberFormatException when JSP is not found. (trace logging) Hi Guys, Well I have trace logging on but there do not appear to be errors in the logs. You can clearly see from the timestamps on the logging below that the errors are linked to each other. As soon as I request a JSP that does not exist, e.g I request http://testserver/nosuchjsp.jsp I get the NumberFormatException in Tomcat stdout and I correctly get the standard Tomcat 404 error page. Does this trace logging help anymore? After the 'processCallbacks status 2', Tomcat will drop the connection to IIS, and certainly not continue with the request. The Tomcat exception should look like an error in the IIS logs. The relevant part of the Jk log is probably the part above this. Cheers, Allistair. This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JK throws java.lang.NumberFormatException when JSP is not found. (trace logging)
] ajp_done::jk_ajp_common.c (1865): recycling connection [Thu Dec 16 16:14:22 2004] [2196:1556] [trace] ajp_done::jk_ajp_common.c (1867): exit -Original Message- From: Bill Barker [mailto:[EMAIL PROTECTED] Sent: 16 December 2004 15:38 To: Tomcat Developers List Subject: Re: JK throws java.lang.NumberFormatException when JSP is not found. (trace logging) - Original Message - From: Allistair Crossley [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Thursday, December 16, 2004 6:22 AM Subject: RE: JK throws java.lang.NumberFormatException when JSP is not found. (trace logging) Hi Guys, Well I have trace logging on but there do not appear to be errors in the logs. You can clearly see from the timestamps on the logging below that the errors are linked to each other. As soon as I request a JSP that does not exist, e.g I request http://testserver/nosuchjsp.jsp I get the NumberFormatException in Tomcat stdout and I correctly get the standard Tomcat 404 error page. Does this trace logging help anymore? After the 'processCallbacks status 2', Tomcat will drop the connection to IIS, and certainly not continue with the request. The Tomcat exception should look like an error in the IIS logs. The relevant part of the Jk log is probably the part above this. Cheers, Allistair. This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT
Re: JK throws java.lang.NumberFormatException when JSP is not found. (trace logging)
- Original Message - From: Allistair Crossley [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Thursday, December 16, 2004 8:18 AM Subject: RE: JK throws java.lang.NumberFormatException when JSP is not found. (trace logging) Hi, OK, just generated it again, and taken more trace ... I can see this ERROR ... [Thu Dec 16 16:14:22 2004] [2196:1556] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (857): ERROR: can't receive the response message from tomcat, network problems or tomcat is down (127.0.0.1:8009), err=-1 Tomcat is *not* down though ;) The tomcat is down is IIS's response to Tomcat dropping the connection after the exception. It's strange that the 'bad' message and the 'good' retry message seem to be identical (and perfectly valid AJP/1.3 packets). Of course, JK1.2.8-RC1 will send different packets now that Mladen has fixed header parsing, but both forms are valid. In particular, the Content-Length is the string 0. I'd love to see the dump from the Tomcat side if you get a chance. This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
