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=36155>. 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=36155 ------- Additional Comments From [EMAIL PROTECTED] 2007-03-03 06:57 ------- So in org.apache.coyote.Request.recylce(), this.localNameMB.recycle() is not called. If i add that call, the problem is gone too (my first patch has been reverted before testing). The problem is: remoteAddrMB.recycle(), remoteHostMB.recycle(), localAddrMB.recycle() is also not called. And i have no clue why not or is it should actually be called. Anyway: At least localNameMB gets reused without being recycled. So the internal charC contains an old value. setBytes() doesn't clear internal the charC-cache. toChars() reuses the old value. Hence the bug. I admit, that the semantics of the MessageBytes class are a ridle to me. I don't know, why setBytes() shouldn't invalidate the charC cache (even though it invalidates all other cached values). Somebody please explain the semantics of this class to me! And decide, whether setBytes() should clear charC, or not. -- 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]
