> From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Subject: Re: Tomcat thread dump analysis
> > It would appear that logic in your application threads has either > > created a deadlock, or failed to unlock something before > > returning, > That's a tall order unless native code is involved, I believe. Nope, it's terribly easy with java.util.concurrent. For example, you can create Semaphore objects, and then forget to call release() after calling acquire(). It's not block-structured like synchronization constructs built into the Java language. - 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: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
