On Aug 15, 2007, at 10:34 AM, Simon McLean wrote:
On Aug 15, 2007, at 10:05 AM, Simon McLean wrote:
Hi -
I'm a beginner when it comes to profiling an app, so please bear
with the idiot questions :-)
The reason I'm digging into profiling is because we have a
deadlock problem.
I've started up the app using JProfiler and I can see various
threads running. The bit I'm concerned about is the sea of red
highlighting blocked worker threads. When I start the app about 2
thirds of the 16 running worker threads are already blocked, and
within a couple of minutes 15 of them are consistently blocked.
Despite this, the app seems to behave ok.
Should I be worried about this ?
That entirely depends on how they are blocked. You need the stack
traces. They could just be "blocked" waiting for request to come
in and give them something to work on.
Hi Chuck -
Ok, I figured how to get JProfiler to give me a stack trace :-)
All of them are blocked here:
com.clicktravel.travelpoint.Application.main(java.lang.String[ ])
Bar one at the moment which is at the same point, but rather than
blocked it's status is "Net I/O".
There should be more to the trace than that.
I've noticed (thanks to your input) that whenever I click around
the app, a couple of the blocked worker threads spring into action
and then go back to their blocked state, so I'm guessing there are
ok sitting at the point detailed above.
What you are describing sounds normal for idle worker threads.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
