[
https://issues.apache.org/jira/browse/OAK-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6720:
-------------------------------
Component/s: core
> The path should be included in the TRACE log of reads
> -----------------------------------------------------
>
> Key: OAK-6720
> URL: https://issues.apache.org/jira/browse/OAK-6720
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.7.8
> Reporter: Jörg Hoh
> Priority: Minor
>
> When I enable the TRACE logging of read requests (setting
> org.apache.jackrabbit.oak.jcr.operations.reads to TRACE) I get this result:
> 26.09.2017 15:39:15.530 *TRACE* [0:0:0:0:0:0:0:1 [1506433155519] GET
> /foo.html HTTP/1.1] org.apache.jackrabbit.oak.jcr.operations.reads
> [session-2620413] getValue
> 26.09.2017 15:39:15.530 *TRACE* [0:0:0:0:0:0:0:1 [1506433155519] GET
> /foo.html HTTP/1.1] org.apache.jackrabbit.oak.jcr.operations.reads
> [session-2620413] getItemOrNull
> 26.09.2017 15:39:15.530 *TRACE* [0:0:0:0:0:0:0:1 [1506433155519] GET
> /foo.html HTTP/1.1] org.apache.jackrabbit.oak.jcr.operations.reads
> [session-2620413] hasProperty
> It would be good if the path where this read operation happens, would be
> logged as well. As it is on TRACE level and should be rarely used, even a
> performance impact would be acceptable.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
