[OAK-3476] Memory leak caused by using marker names based on non static session id

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.0.23, 1.2.8, 1.3.8, 1.4
• Component/s: core
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 06/Oct/15 05:05
• Updated: 02/Mar/16 14:30
• Resolved: 08/Oct/15 06:11

Description

SessionDelegate creates marker based on session id. As session id is variable such markers can get accumulated over time resulting in memory leak [1]

 private static <T> void logOperationDetails(ContentSession session, SessionOperation<T> ops) {
        if (readOperationLogger.isTraceEnabled()
                || writeOperationLogger.isTraceEnabled()
                || auditLogger.isDebugEnabled()) {
            Marker sessionMarker = MarkerFactory.getMarker(session.toString());
            Logger log = ops.isUpdate() ? writeOperationLogger : readOperationLogger;
            log.trace(sessionMarker, "[{}] {}", session, ops);

Workaround

Untill we fix it in code user should just set log level to info for following loggers

• org.apache.jackrabbit.oak.audit
• org.apache.jackrabbit.oak.jcr.operations.reads

[1] http://stackoverflow.com/q/31524084/1035417