Re: BLOCKED threads

2014-05-06 Thread Mark Thomas
On 03/05/2014 02:37, Martin Gainty wrote: > Managing Provider Tokens > Like the provider, the consumer must be responsible for managing the > OAuth tokens. The necessary interface for managing the consumer tokens > is OAuthConsumerTokenServices which are only accessible via factory method. > Ass

Re: BLOCKED threads

2014-05-05 Thread Rallavagu
Logs are written to local disk. Don't have data on disk stats. Thanks. > On May 5, 2014, at 7:19 AM, Daniel Mikusa wrote: > >> On May 3, 2014, at 9:08 PM, Rallavagu wrote: >> >> Here is the thread BLOCKED waiting on another lock. >> >> "http-bio-28080-exec-613" daemon prio=10 tid=0x7fcbac

Re: BLOCKED threads

2014-05-05 Thread Daniel Mikusa
On May 3, 2014, at 9:08 PM, Rallavagu wrote: > Here is the thread BLOCKED waiting on another lock. > > "http-bio-28080-exec-613" daemon prio=10 tid=0x7fcbac0e0800 nid=0x7897 > waiting for monitor entry [0x7fcb915d3000] > java.lang.Thread.State: BLOCKED (on object monitor) >at

Re: BLOCKED threads

2014-05-03 Thread Rallavagu
Here is the thread BLOCKED waiting on another lock. "http-bio-28080-exec-613" daemon prio=10 tid=0x7fcbac0e0800 nid=0x7897 waiting for monitor entry [0x7fcb915d3000] java.lang.Thread.State: BLOCKED (on object monitor) at java.util.logging.StreamHandler.publish(StreamHandler.j

Re: BLOCKED threads

2014-05-03 Thread Rallavagu
Chris, Thanks for the reply. Sorry for not being very clear. Actually, those two threads holding the locks that caused other threads to be blocked. Here is one of the threads that was blocked because of lock on StandarClassLoader. There are around 47 threads in BLOCKED state waiting on the sa

Re: BLOCKED threads

2014-05-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rallavagu, On 5/2/14, 6:22 PM, Rallavagu wrote: > Tomcat Version: 7.0.47 JVM Version: 1.7.0_51-b13 > > I see many blocked threads (90) in the thread dump. There are > mainly two monitors that block 69 threads. > > One of them is below. It appears

RE: BLOCKED threads

2014-05-02 Thread Martin Gainty
Managing Provider Tokens Like the provider, the consumer must be responsible for managing the OAuth tokens. The necessary interface for managing the consumer tokens is OAuthConsumerTokenServices which are only accessible via factory method. Assuming that the consumer can leverage an active HTTP

Re: Blocked threads in Tomcat web app

2009-07-13 Thread Raphael Neve
Rainer Jung-3 wrote: > > > You might want to look at Bloch's book "Effective Java", which has a > section called "Avoid finalizers". The page > > http://java.sun.com/developer/technicalArticles/javase/finalization/ > > also has some introductory material. > > The dbcp pool for instance has

Re: Blocked threads in Tomcat web app

2009-07-13 Thread Rainer Jung
On 13.07.2009 11:31, Raphael Neve wrote: > > Rainer Jung-3 wrote: >> >> [...] >> >> Yup, and the code run by the finalizer makes a network call (likely to >> the database), which seems to be a very bad pattern. Finalizers are not >> a great idea by themselves, but one needs to keep them as simple

Re: Blocked threads in Tomcat web app

2009-07-13 Thread Raphael Neve
Rainer Jung-3 wrote: > > > [...] > > Yup, and the code run by the finalizer makes a network call (likely to > the database), which seems to be a very bad pattern. Finalizers are not > a great idea by themselves, but one needs to keep them as simple as > possible. Doing network communication in

Re: Blocked threads in Tomcat web app

2009-07-13 Thread Rainer Jung
On 13.07.2009 11:05, Raphael Neve wrote: > > Rainer Jung-3 wrote: >> TP-Processor16 owns lock at 0x73a71c40 and thus blocks TP12, TP5 and TP1. >> >> TP16 and TP2 both wait for lock 0x73a71dd0. The thread holding this lock >> is not in your dump. >> >> Since the lock is of type >> org.firebirdsql.g

Re: Blocked threads in Tomcat web app

2009-07-13 Thread Raphael Neve
Rainer Jung-3 wrote: > > TP-Processor16 owns lock at 0x73a71c40 and thus blocks TP12, TP5 and TP1. > > TP16 and TP2 both wait for lock 0x73a71dd0. The thread holding this lock > is not in your dump. > > Since the lock is of type > org.firebirdsql.gds.impl.wire.isc_db_handle_impl, it seems eith

Re: Blocked threads in Tomcat web app

2009-07-13 Thread Rainer Jung
On 13.07.2009 10:12, Raphael Neve wrote: > Hello all, > > I have a problem with a web application using Tomcat 5.5.27 under Fedora > Linux and database Firebird 2.1. > > The application runs fine for a day or so, then I begin getting blocked > threads. Eventually, the heap space runs out and the

Re: Blocked threads in tomcat

2008-11-01 Thread Mohit Anchlia
On Fri, Oct 31, 2008 at 5:52 PM, Caldarale, Charles R <[EMAIL PROTECTED]> wrote: >> From: emerson cargnin [mailto:[EMAIL PROTECTED] >> Subject: Blocked threads in tomcat >> >> Below is the JConsole result, you can see that there are a lot of >> blocked threads on there. >> >> Stack trace: >> java.l

RE: Blocked threads in tomcat

2008-10-31 Thread Caldarale, Charles R
> From: emerson cargnin [mailto:[EMAIL PROTECTED] > Subject: Blocked threads in tomcat > > Below is the JConsole result, you can see that there are a lot of > blocked threads on there. > > Stack trace: > java.lang.Object.wait(Native Method) > org.apache.commons.httpclient.MultiThreadedHttpConnectio

Re: Blocked threads

2008-10-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, Mark Thomas wrote: > Sounds like you have a connection leak. There are various techniques for > tracking these down. One I like is setting the connection pool size to 1 in > your dev environment and then running your tests. +1 I always use a

Re: Blocked threads

2008-10-22 Thread Mark Thomas
Darren Kukulka wrote: > Hi, > > > > We've got a Tomcat 6.0.13 server running a single application under > 64-bit windows with 64-bit SUN JDK 1.6_03 > > > > It runs into situations where a large number of blocked threads appear > that seem to relate to hibernate functions unable to obtain da