> From: Wade Chandler [mailto:[EMAIL PROTECTED] > Subject: Re: Tomcat/JVM hangs in session.getAttribute / HashMap.get() > > so it's not just a getAttribute call or even > 50 million of them alone going to cause HashMap to > lock, but rather the Object being in an intermediate > step when get is called.
Or the HashMap may have been left in an indeterminate state due to concurrent unsynchronized set requests at some point in the past. A single get can later stumble into the situation and hang in a loop. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
