[
https://issues.apache.org/jira/browse/SLING-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595231#action_12595231
]
Bertrand Delacretaz commented on SLING-3:
-----------------------------------------
Added RequestProgressTrackerLogFilter in revision 654519, logs
RequestProgressTracker info at the DEBUG level, with a unique identifier for
each request.
Example output:
REQUEST_117 - 0 (2008-05-08 15:26:32) Starting Request Processing
REQUEST_117 - 2 (2008-05-08 15:26:32) Starting ResourceResolution
REQUEST_117 - 4 (2008-05-08 15:26:32) URI=/index.html resolves to
Resource=JcrNodeResource, type=nt:file, path=/index.html, elapsed = 2ms
REQUEST_117 - 4 (2008-05-08 15:26:32) Starting ServletResolution
REQUEST_117 - 9 (2008-05-08 15:26:32) URI=/index.html handled by
Servlet=DefaultGetServlet, elapsed = 5ms
REQUEST_117 - 10 (2008-05-08 15:26:32) Starting
org.apache.sling.servlets.DefaultGetServlet#0
REQUEST_117 - 10 (2008-05-08 15:26:32)
org.apache.sling.servlets.DefaultGetServlet#0, elapsed = 0ms
That's only a first step towards making the RequestProgressTracker info
available, of course having it in the generated pages would be useful as well.
> Use RequestProgressTracker to log request processing steps
> ----------------------------------------------------------
>
> Key: SLING-3
> URL: https://issues.apache.org/jira/browse/SLING-3
> Project: Sling
> Issue Type: Improvement
> Components: Core, JSP, Resource, Scripting, ServletResolver
> Reporter: Felix Meschberger
>
> The RequestProgressTacker interface defines an API which may be used to track
> the process of request processing. Parties taking part in request processing,
> most notably resource resolution, script and servlet resolution and also
> request filters should track their progress in the tracker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
