BTW The Qpid code does not call IdentityHashMap.Iterator.remove(), which is the source of the problem. So it is probably ok, even so, a HashMap might be safer.
On 02/10/2007, Robert Godfrey <[EMAIL PROTECTED]> wrote: > > From our side what we want to do with the Java is have all the remaining > M2 > JIRAs closed (which we believe will be done by the end of today) and then > just have the tests run in a continuous loop for a couple of days to > satisfy > ourselves that there are no remaining race conditions. > > -- Rob > > On 01/10/2007, Carl Trieloff <[EMAIL PROTECTED]> wrote: > > > > > > Thanks for the update. > > Carl. > > > > Robert Greig wrote: > > > On 01/10/2007, Carl Trieloff <[EMAIL PROTECTED]> wrote: > > > > > >> Where are we in relation to cutting a new M2 release? > > >> > > > > > > We are, we believe, very close. > > > > > > You will not believe this but we have found a bug in > > > java.util.IdentityHashMap which was the cause of one of the hangs that > > > we see periodically. Unfortunately the IdentityHashMap is used in a > > > MINA class. > > > > > > We have a reproducible isolated test case and I am going to raise it > > > with Sun but obviously in this case we are going to look for a > > > workaround. There is no semantic need to use an IdentityHashMap and > > > regular HashMap does not exhibit this bug so we should be able to > > > apply a workaround in our code. We also found usage of IdentityHashMap > > > in a similar situation in the Qpid code which we are going to > > > remediate too. > > > > > > I'll send another update tomorrow morning UK time, also detailing any > > > other jiras that are remaining (I know a good number got updated > > > today). > > > > > > RG > > > > > > > >
