Dump the threads' stack traces if a thread cannot acquire the lock on a page instance

It would be useful if Wicket dumps the stacks of all threads or at least of the thread that holds the lock of a page if another thread cannot acquire this lock for the specified timeout duration.
Currently we just WARN that a threadB cannot acquire the lock because another thread holds it for more then a minute. If the developer wants to debug this she will need to reproduce the problem somehow and then dump the stacks with jstack, kill -3, jconsole, ...
It will be nice if Wicket does that when the problem happens and save some time of the developer.