[
https://issues.apache.org/jira/browse/SLING-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated SLING-6119:
-----------------------------------
Summary: Log parameters not captured correctly in few cases (was: Log
parameters not captures correctly in few cases)
> Log parameters not captured correctly in few cases
> --------------------------------------------------
>
> Key: SLING-6119
> URL: https://issues.apache.org/jira/browse/SLING-6119
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: Log Tracer 1.0.2
>
>
> Tracer also captures the log message parameters separately and provides
> string representation in recording. In some cases where params are bound to
> say JCR session there evaluation fails if done outside of session. This
> causes message like
> {noformat}
> {
> timestamp: 1475920906003,
> level: "TRACE",
> logger: "org.apache.jackrabbit.oak.jcr.operations.writes",
> message: "[session-1987] Setting property
> [/content/dam/summer_collection/jcr:content/jcr:title]",
> params: [
> "session-1987",
> "[FAILED toString()]"
> ]
> }
> {noformat}
> As a fix the param should be converted to string at time of logging itself
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
