>Yep that is it. You are using the old BIO AJP connector based on the >classes you are loading. Hmm. Not what I was expecting. It might be >worth taking a look at this bug: >https://issues.apache.org/bugzilla/show_bug.cgi?id=50189
>The problem is that we need a test case to investigate this but the >issue is hard to reproduce. Since you have a test environment where you >can repeat this, what are the chances of getting a Wireshark trace of >the AJP traffic for a connection where this happens? >Mark >Thanks Mark. >I looked at the bug and noticed the 5.5 fix will be included in 5.5.34. Any idea when this comes out? We >were going to try to upgrade anyway, but maybe we should just wait for 5.5.34. >I would be happy to supply you with a trace, but right now we're unable to reproduce. We're trying, but >coming up with nothing. Any ideas/suggestions on how to reproduce would be great. We are unable to reproduce the bugs listed above and are unsure how to proceed at this point. Mark had mentioned that we are using the "old BIO AJP connector ". Is this something we should change? Anyone have any suggestions on changes to try or ways to reproduce? -- View this message in context: http://old.nabble.com/Response-Swapping-tp31185040p31278390.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
