Description dave debugger 2020-07-29 13:27:24 EDT

When I set a Method breakpoint, of type Exit, in Eclipse with any log4j2 logging instantiated in a class then there's an approx 20 second delay before the program starts.  This delay is not present on the same project when the logging instantiation is commented out.  No actual logging needs to take place for this behaviour to manifest itself.

So this simple project in Eclipse is fine:

package slowdebug;
public class SlowDebug {

 public static void main(String[] args) { 
  System.out.println("Hello world"); 
  thisWontTakeLong(); 
  System.out.println("The end"); 
 }

 private static void thisWontTakeLong() { 
  System.out.println("BRB"); 
 } 
}

But adding the 2 log4j2 jars to the project and adding: 

 private static Logger logger = LogManager.getLogger(SlowDebug.class);
 
and setting a Method exit breakpoint on thisWontTakeLong(), editing it to make it an exit breakpoint not an entry one and the delay appears.

The delay occurs even if the call to thisWontTakeLong() is commented out. It doesn't seem to matter which method has the exit breakpoint.

 

I'm using log4j2 v2.13.3 on Windows 10 Enterprise, Eclipse Version: 2020-06 (4.16.0) Build id: 20200615-1200, Java SE14 (14.0.2, the open source one)

I opened a ticket on the log4j2 bug tracker (https://issues.apache.org/jira/browse/LOG4J2-2900) but really it's hard to see how it's a log4j2 issue