-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Filip,
Filip Hanik - Dev Lists wrote: |> In fact, you still are not covered, because removing the object from the |> session merely removes the reference. If the session replicator is |> running and copying, say, a Map to another machine in the cluster, you |> can't even remove it from the session in order to modify it: you /must/ |> make a copy of it and work on the copy. |> |> That's ridiculous IMHO. | | read the source code and enlighten yourself instead of making | assumptions and making comments like that. Thanks for the condescending attitude, dude. I appreciate it. Which source code do you suggest? |> I'm not sure it would... iterating over a collection (which I assume is |> what the session replicator is doing) while another thread (a request) |> is making legitimate changes to it would lead to a CME no matter what |> replication technology is being used. | | even terracotta is open source, read the source code there, and correct | yourself I'm not interested in terracotta. I'm interested in how Tomcat reacts. The OP said that it was blowing up. I'm positive it was his code doing the concurrent modification of the Map. That's not the problem. From your comments, it seems like you aren't allowed to modify any collections in the session for fear of interfering with the replicator. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkeZCXIACgkQ9CaO5/Lv0PBYQQCePVmHM8SVwBLM2f1ALDdcSXaM aucAnjgViqbZA0GnIpCuhYntUx9v2OTw =kVv9 -----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]
