Project

General

Profile

Feature #3307

enhance LockAdministrator implementation to collect info on sessions waiting to lock a record

Added by Eric Faulhaber almost 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD

Related issues

Related to Runtime Infrastructure - Feature #3222: rewrite admin console for native web (html5/css/javascript) Closed

History

#1 Updated by Eric Faulhaber almost 4 years ago

Having this information would help greatly in tracking down the root cause of deadlock conditions. Currently, we only collect information on locks successfully acquired, but this is only part of the equation. Knowing which session is blocked, waiting to acquire a particular lock, is another part.

Yet another useful bit of information is the location in the code that the lock was acquired, and still another is the location in the code of the session currently attempting to acquire it. These last two data currently are collected for FINE and higher logging on the com.goldencode.p2j.persist.lock.LockManager logger, but the current implementation generates a stack trace for every lock acquisition, which is prohibitively expensive in a production system. Also, changing the log level requires a server restart. These items are out of scope for this issue.

Once the lock manager implementation is enhanced, the FWD Administration Console will have to be updated to present the waiting session information.

#2 Updated by Eric Faulhaber almost 4 years ago

  • Related to Feature #3222: rewrite admin console for native web (html5/css/javascript) added

Also available in: Atom PDF