[jira] Commented: (WICKET-433) improved reporting on locked page maps

["Matej Knopp (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495262 ] 

Matej Knopp commented on WICKET-433:
------------------------------------

Even more useful would be to have the stack-strace. I think we can do that, but only for java 5. So what we should do is an extension point where user could plug in a class that would write a stacktrace for him (if he uses 1.5).


> improved reporting on locked page maps
> --------------------------------------
>
>                 Key: WICKET-433
>                 URL: https://issues.apache.org/jira/browse/WICKET-433
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.3
>            Reporter: Eelco Hillenius
>         Assigned To: Johan Compagner
>             Fix For: 1.3
>
>
> It would be cool if we could log some more information on which request is locking another request when it times out. Currently, we get an error like:
> exception: After 1 minute the Pagemap null is still locked by: Thread[Jetty thread-105,5,main], giving up trying to get the page for path: 0:1
> but Thread[Jetty thread-105,5,main] is hardly useful in a log. More useful would be e.g. the request target.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.