DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35461>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35461 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-19 00:48 ------- (In reply to comment #10) > Same problem here. Please let us know how we can help debugging that issue. > Thanks > Alex It's pretty clear what is happening: mod_jk isn't sending the POST body before the Tomcat-configured connectionTimeout has been reached. What isn't clear is why. In the first dump example, the worker in the JSESSIONID cookie isn't in the list (there are also some decoding problems, but they shouldn't affect Tomcat). In the second dump example, mod_jk has decided to send the request to a different worker than the one in the cookie for some reason. Otherwise, they are perfectly normal POST request records. Probably, somebody is going to have to be able to reproduce this with 'JkLogLevel debug' (or even 'JkLogLevel trace' :) to get some idea why the POST body wasn't sent. As an aside, Tomcat 5.5.11+ won't have this particular error, but it is also extremely unlikely to actually work. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
