[LOG4J2-1452] Reusable messages break flow tracing logic

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6, 2.6.1
• Fix Version/s: 2.6.2
• Component/s: Core
• Epic Link: GC-free
• Assignee: Remko Popma
• Reporter: Mikael Ståldal
• Created: 29/Jun/16 19:38
• Updated: 18/Sep/16 10:37
• Resolved: 18/Sep/16 10:37

Description

Flow tracing assumes that you can save an instance of EntryMessage across a method, but if you log something else within that method and reusable messages are in effect (as they are by default since 2.6), this does not always work properly.

This code illustrate the issue:

        EntryMessage entryMessage = logger.traceEntry(logger.getMessageFactory().newMessage("the entry"));
        logger.info("something else");
        logger.traceExit(entryMessage);

It works as expected if you remove the middle logger.info(), but with it the exit message gets messed up.