This discussion is archived
3 Replies Latest reply: Oct 17, 2012 3:08 AM by Ganesh.. RSS

What decides a thread as Stuck?

user769080 Newbie
Currently Being Moderated
In WebLogic there are two places where "the number of seconds that a thread must be continually working before this server diagnoses the thread as being stuck" can be set:

(1) Stuck Thread Max Time (from Admin Console: Server > Configuration > Tuning)
In the config.xml this corresponds to:
<server>
...
*<stuck-thread-max-time>n1</stuck-thread-max-time>*
...
</server>

(2) Max Stuck Thread Time (from Admin Console: Server > Configuration > Overload)
In the config.xml this corresponds to:
<server>
...
<overload-protection>
<server-failure-trigger>
*<max-stuck-thread-time>n2</max-stuck-thread-time>*
...
</server-failure-trigger>
</overload-protection>
...
</server>

When the values for these two elements do not match which one of them will finally define the threshold that decides if a thread is stuck?
  • 1. Re: What decides a thread as Stuck?
    Kalyan Pasupuleti-Oracle Expert
    Currently Being Moderated
    Hi,

    First one is main to increase the stuck thread time out.

    Not second one... as it have different purpose to set max stuck thread time.


    Regards,
    Kal
  • 2. Re: What decides a thread as Stuck?
    868652 Newbie
    Currently Being Moderated
    I also met this problem, I had to tunning our application. Please support us for tunning the managed server to avoid this problem. Thansk so much.
  • 3. Re: What decides a thread as Stuck?
    Ganesh.. Explorer
    Currently Being Moderated
    Hi,
    Default time for a thread to be termed as stuck is 600 seconds which is 10mins and it is specifed by 'Stuck Thread Max Time'. You can change the value as per the performance of your applications. But if any thread in application is taking so long to complete then there is some serious flaw in the application which needs to be corrected quickly. If this is a valid case (e.g. singleton), then you can specify any valid value. But there is always risk in it that if on serious contention, all the threads will be in active state without any notification in the weblogic console until the stuck thread time is reached.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points