Ah, good point. Hadn't quite thought that one through. Don't really know what to say about that one. Someone else, I think, will have to address that.
-Jason On Wed, 2002-09-25 at 13:17, Cornelius Keller wrote: > Hi Jason, > > I ve read the Javadoc you posted well. > > > Jason McKerr wrote: > > This likely is not an OJB issue. Either that or somewhere OJB is > > iterating over and modifying a collection at the same time. The tw > > should be split to prevent this from happening. > > In my opinion exactly this could happen in the singlevm > PersitenceBrokerImpl if you have more then one Instance of it in the > same JVM. It iterates over Collections coming out of the metadata Layer > wich is accessable form every PB instance and due to this not thread-safe. > > My Patch solved that Problem for me, I am not shure if it will do for > the Originator of this Thread, cause as I read now in his stacktrace he > used the ODMG api. But I posted it in case it is usefull. > > > > Here's the javadoc for this issue. > > > > >http://java.sun.com/j2se/1.4/docs/api/java/util/ConcurrentModificationException.html > > > > > [...] > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
