Closed GoogleCodeExporter closed 9 years ago
It doesn't matter with xmemcached.
It seems that you set a object with a ArrayList instance inside,and when you
set the object ,another thread has modified the array list instance,so it throw
the ConcurrentModificationException when serialized the array list instance.
Original comment by killme2...@gmail.com
on 26 Oct 2012 at 3:11
[deleted comment]
So is XMemcachedClient threadsafe in general? Seems like you are suggesting
that the issue here is just that two threads are operating on the object being
serialized? I guess that makes sense the exception is coming from within
serialize.
- Taylor
Original comment by tlees...@gmail.com
on 26 Oct 2012 at 3:20
Yes,XmemcachedClient is threadsafe.
The exception is coming from within serialize a ArrayList instance,and someone
modified the instance such as adding/removing objects from it,then it caused
the serializer throw the exception.
Original comment by killme2...@gmail.com
on 26 Oct 2012 at 3:23
Original comment by killme2...@gmail.com
on 21 Nov 2012 at 10:12
Original issue reported on code.google.com by
tlees...@gmail.com
on 26 Oct 2012 at 12:12