An Even Better TimedLock

code 0 comments suggest edit

Wow! After posting my update to the TimedLock class entitled TimedLock Yet Again Revisited…, Ian Griffiths posts this gem which outlines a solution to one of the problem’s with my approach to keeping a stack trace.

The problem is that my code acquires a stack trace every time it acquires a lock just in case another thread fails to acquire a lock. The purpose of this action is so that we can examine the stack trace of the blocking thread to find out why we couldn’t acquire a lock. This can be a big performance cost in some situations.

Ian received the solution via an email from Marek Malowidzki. Marek, if you’re out there. I’d love to see the proof of concept code you wrote. I won’t rehash the explanation of the solution, but will mention that it avoids creating and storing a StackTrace every time a lock is acquired, and rather, finds a way to obtain the blocking thread’s stack trace if and only if another thread fails to acquire a lock. How? You have to read the Ian’s post to find out.

Found a typo or error? Suggest an edit! If accepted, your contribution is listed automatically here.



0 responses