tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <>
Subject RE: jvm cowardly refuses to print a thread dump
Date Tue, 02 Dec 2008 14:16:26 GMT

so the solution is put all updates/inserts to the arraylist into a synchronized method?Martin
______________________________________________ Disclaimer and confidentiality note Everything
in this e-mail and any attachments relates to the official business of Sender. This transmission
is of a confidential nature and Sender does not endorse distribution to any party other than
intended recipient. Sender does not necessarily endorse content contained within this transmission.
> To:> From:> Subject: Re:
jvm cowardly refuses to print a thread dump> Date: Tue, 2 Dec 2008 14:35:33 +0100> >
Leon Rosenberg wrote:> > But back to the ArrayList, how high is the probability of having>
> ArrayList.size() twice in the similar call-tree in one ThreadDump?> > > >
Very likely you have unsynchronized accesses to the ArrayList, which > from time to time
send one of the threads involved into an infinite > tight loop inside an ArrayList access
function. A way to confirm this > is to take two thread dumps a minute apart; if you find
the *same* > threads in the same ArrayList access functions, they loop infinitely.>
> Regards,> > Oliver Schoett> > > --------------------------------------------------------------------->
To start a new topic, e-mail:> To unsubscribe, e-mail:>
For additional commands, e-mail:> 
Send e-mail anywhere. No map, no compass.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message