[LOG4J2-1295] Automated testing to verify no temporary objects allocated in gc-free configuration

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5
• Fix Version/s: 2.6
• Component/s: API, Configurators, Core, Layouts, Pattern Converters
• Epic Link: GC-free
• Assignee: Remko Popma
• Reporter: Remko Popma
• Created: 23/Feb/16 06:01
• Updated: 17/May/16 13:30
• Resolved: 15/Mar/16 06:37

Description

LOG4J2-1270 proposes changes to support gc-free behaviour (no allocation of temporary objects) in certain configurations.

This ticket is about verifying that Log4j does not allocate in these configurations. It is not always obvious that some code creates objects, so it is easy for regressions to creep in during maintenance code changes.

Ideally this verification is packaged so it can run automatically during the test phase of the build, for example in a JUnit test.

Issue Links

• is related to: LOG4J2-1388 Upgrade allocation-instrumenter from 3.0 to 3.0.1