I said the Map could be corrupted because i dint view it as a JVM bug :). When i went through the code found like synchronization was taken care. I will dig in more into this. Thanks Stack.
Regards Ram -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stack Sent: Wednesday, November 02, 2011 7:30 PM To: [email protected]; [email protected] Subject: Re: client thread waiting infinitely On Tue, Nov 1, 2011 at 11:23 PM, Ramkrishna S Vasudevan <[email protected]> wrote: > JVM version is 1.6. There was no profiling done. > In the TreeMap remove method we try to compare and then remove. So may be > its not able to find the intended key as the map is corrupted and hence the > comparator is stuck and runs infinitely. > Is it a recent 1.6 JVM? Perhaps a bug in JVM? Otherwise, can you reproduce? Why you think the Map 'corrupt'? St.Ack
