yes, definitely.
Bryan Pendleton wrote:
A long time ago there use to be room in each lock to point at a
stack trace for each lock, but that was removed...
Would it be reasonable for me to file an enhancement request on this?
It seems like you've outlined several possible alternate implementat
A long time ago there use to be room in each lock to point at a
stack trace for each lock, but that was removed...
Would it be reasonable for me to file an enhancement request on this?
It seems like you've outlined several possible alternate implementations
that might be viable, and it definitel
It is a bug in the article, I will need to check if the documentation
has the same problem. I think it was a wish that never came to be.
A long time ago there use to be room in each lock to point at a
stack trace for each lock, but that was removed to optimize the size
of the lock data structure
Hi all,
I was reading http://www.linux-mag.com/content/view/2134/
(good article, btw!), and it says:
The next two properties are needed to diagnose concurrency
(locking and deadlock) problems.
*derby.locks.monitor=true logs all deadlocks that
occur in the system.
*derby.loc
