Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

-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 clust

Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: | no, its just common sense, given that the session should represent a | client state, | and by the time the cluster tries to serialize it, the request is over. There's no guarantee t

Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: | no, its just common sense, given that the session should represent a | client state, | and by the time the cluster tries to serialize it, the request is over. There's no guarantee that the request is complete

Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: | if you look at the stack trace, there is no error in the clustering | code. something is modifying your session attribute while the cluster is | trying to send it I'm suggesting t

Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: | if you look at the stack trace, there is no error in the clustering | code. something is modifying your session attribute while the cluster is | trying to send it I'm suggesting that this should not be conside

Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

if you look at the stack trace, there is no error in the clustering code. something is modifying your session attribute while the cluster is trying to send it Filip Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: | the solution

Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: | 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 What's wrong with modifying something in a sessio

Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

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 cl

Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

-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 onl

Re: ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

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 org.apache.commons.collections.LRUMap Filip LERBSCHER JEAN-PIERRE wrote: Hi, We work on Tomcat clustered server (5.5) and we have thi

ConcurrentModificationException on tomcat cluster with SimpleTcpCluster strategy

Hi, We work on Tomcat clustered server (5.5) and we have this exception in the log (at 5-10 TPS). Could you explain us what's hapenning. Have you a solution? Thanks. Exception: SEVERE: Failed to serialize the session! java.util.ConcurrentModificationException at org.apac