[
https://issues.apache.org/jira/browse/WICKET-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848722#action_12848722
]
Vincent commented on WICKET-433:
--------------------------------
Although the log message is very useful, it cannot be disabled. In case of a
malicious user, this can fill up the log quite fast. Our administrators
therefore have a problem with this message (although this can be controlled by
throttling users at the web server in front of the application server).
Isn't it possible to use setStackTrace (see Throwable.java) instead? That means
I can output the trace on debug level but suppress it on error level using my
favorite logging framework.
I can create a proof a concept for this solution, if anyone can comment if this
change would indeed be desirable.
> 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.
