Re: What could cause a Thread.sleep(500) to block forever?
- From: Laurenz Albe <invite@xxxxxxxxxxxxxxx>
- Date: 19 Mar 2008 07:42:00 GMT
david.karr <davidmichaelkarr@xxxxxxxxx> wrote:
I'm helping to diagnose a problem with a Java app running in WebLogic
9.2.2 on AIX 5.3, using the 64-bit JVM.
For some reason we're seeing a thread get stuck in an odd place. It's
sitting on a "Thread.sleep(500L)" (that's 500 milliseconds). It seems
like the Thread.sleep() call doesn't return, and just hangs there.
This doesn't happen all the time, but when it gets to this point, we
have to restart the WLS instance.
What sort of things could cause this, and what kinds of information
could I gather to get more information?
How did you verify that the process really stays in Thread.sleep()?
Could it be that you are caught in an endless loop that happens to
include a Thread.sleep(), e.g. while waiting for something?
Yours,
Laurenz Albe
.
- Follow-Ups:
- Re: What could cause a Thread.sleep(500) to block forever?
- From: david.karr
- Re: What could cause a Thread.sleep(500) to block forever?
- References:
- What could cause a Thread.sleep(500) to block forever?
- From: david.karr
- What could cause a Thread.sleep(500) to block forever?
- Prev by Date: Re: question about aix licencing?
- Next by Date: Linux Toolbox CD for AIX 5.2/5.3?
- Previous by thread: What could cause a Thread.sleep(500) to block forever?
- Next by thread: Re: What could cause a Thread.sleep(500) to block forever?
- Index(es):
Relevant Pages
|
