Closed valters closed 5 years ago
I just saw the same exception when testing with j256 CW appender. So I think it's simply issue that Spring logback shutdown hook has/causes. It's not specific to dibog appender.
06:41:09.452| INFO|done
Exception in thread "Thread-1" java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at java.util.ArrayList.batchRemove(ArrayList.java:730)
at java.util.ArrayList.retainAll(ArrayList.java:715)
at ch.qos.logback.classic.LoggerContext.resetListenersExceptResetResistant(LoggerContext.java:305)
at ch.qos.logback.classic.LoggerContext.reset(LoggerContext.java:227)
at ch.qos.logback.classic.LoggerContext.stop(LoggerContext.java:348)
at org.springframework.boot.logging.logback.LogbackLoggingSystem$ShutdownHandler.run(LogbackLoggingSystem.java:327)
at java.lang.Thread.run(Thread.java:748)
Hi @valters,
I nevertheless looked into the source code of LoggerContext and also could not see how my appender could influence this exception.
Thanks for bringing this issue forward.
Best regards, Dieter
PS: Sorry for the late reaction.
Hi,
I am sometimes seeing strange exceptions while logback is shutting down. This has never happened before (also when I was using j256 logback appender), and somehow it seems to me it might be introduced by this appender... I have no idea how, but here goes:
And
This seems rather rare, and I would not know how to repro this. Maybe you will have some idea how it could happen? Seems to happen when exiting quickly from the app (i.e., when it has nothing to do). My use-case is a command line app for which I need to push the logs into CW.
I am running Amazon Coretto OpenJDK 11 LTS.