When you apply response time thresholds to components, the server may deadlock if the thread monitors used do not allow nesting.
The thread monitor Allow Nesting (allowNesting) property specifies whether thread monitor limits are applied when a thread already holds another monitor. For example, if a thread has already acquired monitor A, nesting allows the thread to acquire monitor B even if B's usage level is above the maximum. Nesting is allowed by default.
Allowing nesting prevents deadlock. Deadlock may occur in some intercomponent call scenarios if you disable thread monitor nesting for the thread monitor used in response-time threshold monitoring. If you suspect your components may be deadlocked due to response-time monitoring, analyze the stack traces in the performance monitor statistics.
