Dump the threads' stack traces if a thread cannot acquire the lock on a page
instance
--------------------------------------------------------------------------------------
Key: WICKET-4170
URL: https://issues.apache.org/jira/browse/WICKET-4170
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 1.5.2
Reporter: Martin Grigorov
Assignee: Martin Grigorov
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
