We are seeing a situation where the consumer thread "AsyncLoggerConfig-1" is apparently dying. We do see a new consumer thread trying to start up, but it is blocked waiting for a lock, so no logging is happening.
Is this a defect in log4j? Is the original consumer thread dying due to perhaps an unhandled exception ? Is that original consumer thread not terminating gracefully and releasing the locked object so the new consumer thread can start? Please see attached screenshot. Top of screen is normal asyncloggerconfig thread (consumer). Bottom is thread trace when logging stops, we no longer see an "asyncloggerconfig-1" thread, instead a new thread is trying to start but never does "asyncloggerconfig-2".
--------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
