Shortly after this, while pouring through the tomcat issues
repository, I stumbled across this:
http://issues.apache.org/bugzilla/show_bug.cgi?id=41772
After reading, I became more convinced that re-used response objects
was at the heart of my issue. I searched high-and low through my user
Jeff Amiel wrote:
Any advice or thoughts would be appreciated.
Bit of a long shot but it could be re-use of a RequestDispatcher.
Prior to 5.5.21 RD's were not thread-safe so if an RD is cached and
re-used that might explain what you see.
Mark
Have been battling a recent issue (outlined in some detail on the
struts mailing list)
http://www.mail-archive.com/user%40struts.apache.org/msg61515.html
In summary, unless their is some underlying bug that I cannot pinpoint
(always possible), my AxisServlet is being handed off a response that
Jeff Amiel [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Have been battling a recent issue (outlined in some detail on the
struts mailing list)
http://www.mail-archive.com/user%40struts.apache.org/msg61515.html
In summary, unless their is some underlying bug that I cannot
On 6/6/07, Bill Barker [EMAIL PROTECTED] wrote:
It doesn't make sense. The Facade delegates to the actual response always,
so getting a new instance (the security manager option) won't help. My
first guess would be that somebody is doing a jsp:include ... flush=true
But how would that
