[
https://issues.apache.org/jira/browse/SLING-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896773#comment-17896773
]
Remo Liechti commented on SLING-12478:
--------------------------------------
The testdata that I have there is taken from the console of the docker
apache/sling:snapshot and then modified a bit to test the code for cascading
scenarios. 'Request Processing' was in there and obviously is the first
START_TIMER that probably will never have an END_TIMER when we log this
message, so we could potentially strip it.
{quote}entries seem to be logged in a single line, I think one entry per line
would be a better fit.
{quote}
Yes, as we discussed before... This is first of all done because a java
exception message should not contain multi line, and second to support logging
tools better that may have issues with multi line parsing.
If you wish changes to any of those for some reason, please define clear
requirements.
> Add potential origins of violations to the RequestDispatcher include API
> ------------------------------------------------------------------------
>
> Key: SLING-12478
> URL: https://issues.apache.org/jira/browse/SLING-12478
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Remo Liechti
> Assignee: Remo Liechti
> Priority: Minor
> Fix For: Engine 2.16.0
>
>
> Add more information to the log about potential origins of the violation
> message added in SLING-12454.
> Use the RequestProgressTracker API to get the messages to find START_TIMER's
> that do not have an END_TIMER yet, which means a violation is most likely
> caused by that origin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
