You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2008/04/20 20:46:28 UTC
[jira] Updated: (WICKET-433) improved reporting on locked page maps
[ https://issues.apache.org/jira/browse/WICKET-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-433:
--------------------------------------
Fix Version/s: (was: 1.4-M1)
1.4-M2
> 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.0-beta1
> Reporter: Eelco Hillenius
> Assignee: Johan Compagner
> Priority: Minor
> Fix For: 1.4-M2
>
>
> 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.