Ian Long wrote:
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.
I am no Tomcat logging nor log4j exp
2014-04-11 21:47 GMT+04:00 Ian Long :
> 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:
By the way: there is a couple of known errors in 1.2.39 (see
changelog). A vote on 1.2.40 release candidate is currently go
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é War
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 l
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
[
