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=33515>. 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=33515 Summary: Add too big item to request attrbiute in filter Product: Tomcat 5 Version: 5.0.28 Platform: PC OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: Servlet & JSP API AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] If object (in my case SAXSource) is added to request attribute in filter and the object inside attribute is big enough it causes random failures on page load. Usually page is cutted half (end of the page is not sent to browser). I haven't tested how big object should be but seems classical buffer overflow on some point of chain. At least it would be nice to see some exception if object is too big to be handled. Don't know if it matters but I have 3 filters on the filter chain. I added SAXSource at filter 2. I don't think that I should store big object on the request attribute anyway but this was the case in one tester I made. -- 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]