If I remember correctly, there was once a bug along these lines triggered by certain evictions of the prepared statement pool that was addressed in either the pool or dbcp component. Looking through the cvs logs quickly I wasn't able to see it, but you may want to give a recent nightly build a try.
On Fri, 28 Feb 2003, Lee Breisacher wrote: > I just ran into this error: > > java.util.ConcurrentModificationException > at > java.util.AbstractList$Itr.checkForComodification(AbstractList.java:444) > at java.util.AbstractList$Itr.next(AbstractList.java:421) > at > org.apache.commons.collections.CursorableLinkedList.broadcastListableInserte > d(Unknown Source) > at > org.apache.commons.collections.CursorableLinkedList.insertListable(Unknown > Source) > at > org.apache.commons.collections.CursorableLinkedList.addFirst(Unknown Source) > at > org.apache.commons.pool.impl.GenericObjectPool.returnObject(Unknown Source) > > Unfortunately, I do not have stack traces for the other threads that were > running, so I don't know what some other thread must have been doing to > cause this. But, looking at GenericObjectPool, it appears to be properly > synchronized at all the places that operate on the CursorableLinkedList (its > _pool variable), so I don't quite understand how this error can occur. > Anyway, does this look like a bug in CursorableLinkedList? Has anyone seen > this before and know of a fix/workaround? > > Thanks, > > Lee > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
