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 38740] - (5.5.15) session attributes set in sessionCreated not synched
Date Fri, 24 Feb 2006 14:45:14 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=38740>.
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=38740





------- Additional Comments From rainer.jung@kippdata.de  2006-02-24 15:45 -------
Attributes set by a session listener via setAttribute in sessionCreated are not
replicated via the cluster. Only the creation of the session (it's ID) is being
replicated and after the listener was called the DeltaRequest is being reset.

But: if notifySessionListenersOnReplication=true for the cluster manager - which
is the default - then the listener is called after replicating the session
creation on the remote side and will then set the Attribute there again. That's
why the attribute can be found on the remote side.

CAUTION: Replicating an attribute and setting it independently on the primary
and secondary nodes might not be the same. It depends on the type of the
attribute if that results in an application problem 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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message