[ https://issues.apache.org/jira/browse/WICKET-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844996#comment-17844996 ]
ASF subversion and git services commented on WICKET-7110: --------------------------------------------------------- Commit fe11a241c2cabb1a9e18fc3c593aa9f026a373e6 in wicket's branch refs/heads/WICKET-7110 from Martijn Dashorst [ https://gitbox.apache.org/repos/asf?p=wicket.git;h=fe11a241c2 ] WICKET-7110: Apply suggestions from code review Co-authored-by: Martin Grigorov <marti...@users.noreply.github.com> > Add stack trace of lock holding thread in CouldNotLockPageException > ------------------------------------------------------------------- > > Key: WICKET-7110 > URL: https://issues.apache.org/jira/browse/WICKET-7110 > Project: Wicket > Issue Type: Improvement > Reporter: Martijn Dashorst > Assignee: Martijn Dashorst > Priority: Minor > > Currently we only log the stack trace of the thread that keeps the lock on > the page when we can't claim a lock. It is beneficial to set the cause of the > CouldNotLockPageException to an exception that shows the stack trace elements > of the thread holding the lock. > This way you can see in the monitoring what was the cause instead of having > to go look for the holding (e.g. slow) page in the logs. -- This message was sent by Atlassian Jira (v8.20.10#820010)