the solution is to not store stuff in the session modified by other
threads, if that's the case, then its not really something you wanna
store in a session
Filip
Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| this is not a cluster error, basically, you are storing a map in the
| session, and someone is modifying the map while the cluster is
trying to
| replicate it
How should this be solved? The OP could really only synchronize his own
code against either an external monitor, or the Map itself. On the other
hand, how should the application's code interact with the cluster
replication code to avoid such concurrent modifications?
Does the servlet spec provide a mechanism to protect session replication
against this?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkeRKeYACgkQ9CaO5/Lv0PAF5ACeIlYZAami/vJv8q4DJsOuCl0G
v20AoK2+svEmZuyZMJd16P7N8PIfnfMJ
=mTNL
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
