Yes, the error is coming from tomcat for sure. Tomcat is logging my application errors, but I think the 500 error is in Tomcat code. I am trying to find out why tomcat is not logging this error, it logs exceptions that happen in my code.
Cheers, Ian On April 11, 2014 at 2:57:05 PM, André Warnier (a...@ice-sa.com) wrote: Ian Long wrote: > This is a followup to my previous email, about Tomcat 500 errors. For every > error, I see this in the mod_jk (1.2.39) debug logs: > > > [Fri Apr 11 13:06:33.956 2014] [25409:140068250126304] [debug] > ajp_connection_tcp_get_message::jk_ajp_common.c (1403): received from ajp13 > pos=0 len=114 max=16384 > [Fri Apr 11 13:06:33.956 2014] [25409:140068250126304] [debug] > ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0000 04 01 F4 00 15 > 49 6E 74 65 72 6E 61 6C 20 53 65 - .....Internal.Se > [Fri Apr 11 13:06:33.956 2014] [25409:140068250126304] [debug] > ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0010 72 76 65 72 20 > 45 72 72 6F 72 00 00 02 A0 07 00 - rver.Error...... > [Fri Apr 11 13:06:33.957 2014] [25409:140068250126304] [debug] > ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0020 34 6F 61 6D 2E > 46 6C 61 73 68 2E 52 45 4E 44 45 - 4oam.Flash.RENDE > [Fri Apr 11 13:06:33.957 2014] [25409:140068250126304] [debug] > ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0030 52 4D 41 50 2E > 54 4F 4B 45 4E 3D 2D 31 79 76 30 - RMAP.TOKEN=-1yv0 > [Fri Apr 11 13:06:33.957 2014] [25409:140068250126304] [debug] > ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0040 6F 6D 7A 74 68 > 3B 20 50 61 74 68 3D 2F 3B 20 53 - omzth;.Path=/;.S > [Fri Apr 11 13:06:33.957 2014] [25409:140068250126304] [debug] > ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0050 65 63 75 72 65 > 00 A0 01 00 17 74 65 78 74 2F 68 - ecure.....text/h > [Fri Apr 11 13:06:33.957 2014] [25409:140068250126304] [debug] > ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0060 74 6D 6C 3B 63 > 68 61 72 73 65 74 3D 55 54 46 2D - tml;charset=UTF- > [Fri Apr 11 13:06:33.957 2014] [25409:140068250126304] [debug] > ajp_connection_tcp_get_message::jk_ajp_common.c (1403): 0070 38 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 - 8………….. > > Has anyone seen this or have a resolution? ASCII-graphically, your setup is like : Request : Client --> request --> Apache httpd + mod_jk -- request --> Tomcat --> webapp Response : Client <-- response -- Apache httpd + mod_jk <-- response -- Tomcat <-- webapp 500 500 What you are seeing in this log, seems to be a dump, by mod_jk, of a response data packet that it receives from Tomcat. So the error originates in Tomcat, which produces a "500 Server Error" response, with a body consisting of a html page giving some details about the error. This error seems to be produced by an application running within Tomcat, which may have something to do with a "Flash Renderer"..(*) Does that ring a bell ? Now why that 500 error does not appear in your Tomcat logs, may have something to do with the way in which the Tomcat logging is set up (or with you looking in the wrong place). But that is harder to tell from here. But in any case, the 500 error does not originate with mod_jk or Apache httpd. They are just dumping the data that they see go through, coming from Tomcat. (*) Note: that may just be the readable part of a HTTP response header, like a Set-Cookie. It's also hard to tell, not knowing the corresponding request. (The AJP protocol replaces many often-used HTTP header names, by shorter numerical codes). If you look a bit earlier in that log, you should see the request which causes the error. Maybe that will tell you more. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
