tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18479] - HttpSessionBindingListener.valueUnbound() not called
Date Sun, 11 Apr 2004 06:12:59 GMT
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=18479>.
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=18479

HttpSessionBindingListener.valueUnbound() not called





------- Additional Comments From hoju@visi.com  2004-04-11 06:12 -------
I believe the fix for this issue has caused another one.  The Tomcat-5.0.21
changlog says the following about the fix for this bug report...

18479: Non-serializable sessions attributes should be removed (so valueUnbound
is called) (markt)

I have a session that is perfectly serializable in both 5.0.19 and 5.0.20, but
as of 5.0.21, the value for the session attribute comes back null.  I also
tested in 5.0.22 with the same result.  The test consists of a hit counter that
stays in the session and should pick up right where it left off upon
server/application reload as long as the session hasn't yet timed out.

I have a HttpSessionAttributeListener reporting when objects are
added/removed/replaced in the session.  I get the report of the object in
question being added, but I never see that it has been removed or replaced.  As
such, I must assume that the session attribute is still there, but its value
changed to null somewhere behind the scenes in a way that doesn't report it to
the HttpSessionAttributeListener (at a minimum, attributeReplaced() should be
called, no?).

If this report should be separate from this bug, please say so and I'll do that,
but this one seems suspect as the cause for the issue I am seeing.  Also let me
know if more information is needed or if a test case is needed.  I, obviously,
have a test case, but it not exactly simplified.  I'll do that if what I am
reporting seems non-obvious to the Tomcat gurus.

Jake

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message