[
https://issues.apache.org/jira/browse/LOG4J2-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dave debugger updated LOG4J2-2900:
----------------------------------
Summary: Method Exit Breakpoints very slow in Eclipse when using Log4j2
(was: Method Breakpoints very slow in Eclipse when using Log4j2)
> Method Exit Breakpoints very slow in Eclipse when using Log4j2
> --------------------------------------------------------------
>
> Key: LOG4J2-2900
> URL: https://issues.apache.org/jira/browse/LOG4J2-2900
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.13.3
> Environment: I'm using log4j2 on Windows 10 Enterprise, Eclipse
> Version: 2020-06 (4.16.0) Build id: 20200615-1200, Java SE14 (14.0.2, the
> open source one).
> Reporter: dave debugger
> Priority: Minor
>
> I've noticed that if 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 logging is commented out.
> So this simple project in Eclipse is fine:
> {code:java}
> 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");
> }
> }{code}
> But adding the 2 log4j2 jars to the project and adding:
> {code:java}
> private static Logger logger = LogManager.getLogger(SlowDebug.class);
>
> {code}
> 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.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
