Solution? In my days of effort to troubleshoot, I ran across this ditty:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg06836.html Was it possible that my response objects (even committed ones) were being re-used by other requests....and hence be the underlying cause of this? (the setBufferSize() call in the stack trace is because the ResponseFacade is already in a committed state). Sure enough, installed a security manager on tomcat (via jboss) and the problem has apparently 'gone away' (in my development environment). I intend to try this in another (test) environment tomorrow and then eventually production. Does this sound possible? Why would the default behavior for Tomcat be to not destroy these response objects? I assume it's a performance reason....but the unexpected behavior that could result seems unacceptable to me (if this is indeed the cause). But then to that point, why is a security manager not part of the default install either? (http://weblogs.java.net/blog/felipegaucho/archive/2006/01/is_the_security_1.html) Any further insight would be appreciated. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
