[
https://issues.apache.org/jira/browse/WICKET-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848797#action_12848797
]
Johan Compagner commented on WICKET-433:
----------------------------------------
how can a malicious user lock pages/pagemaps so create those kind of errors?
These errors are more or less programming/web application errors that you need
to fix.
> 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.
