You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martijn Dashorst (Jira)" <ji...@apache.org> on 2024/05/09 13:10:00 UTC

[jira] [Assigned] (WICKET-7110) Add stack trace of lock holding thread in CouldNotLockPageException

     [ https://issues.apache.org/jira/browse/WICKET-7110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Dashorst reassigned WICKET-7110:
----------------------------------------

    Assignee: Martijn Dashorst

> 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)