Stefan Egli created OAK-10933:
---------------------------------

             Summary: Avoid log about calculating fullGCTimestamp when fullGC 
is disabled
                 Key: OAK-10933
                 URL: https://issues.apache.org/jira/browse/OAK-10933
             Project: Jackrabbit Oak
          Issue Type: Task
          Components: documentmk
            Reporter: Stefan Egli
            Assignee: Stefan Egli


With fullgc disabled below info message were seen - they should be avoided :
{noformat}
01.02.2013 10:11:12.014 *INFO* 
[sling-oak-1-org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService$RevisionGCJob]
 org.apache.jackrabbit.oak.plugins.document.VersionGCRecommendations No 
fullGCTimestamp found, querying for the oldest modified candidate
01.02.2013 10:11:12.015 *INFO* 
[sling-oak-1-org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService$RevisionGCJob]
 org.apache.jackrabbit.oak.plugins.document.VersionGCRecommendations 
fullGCTimestamp found: 2004-01-02 23:24:25.026
{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to