joepembe commented on issue #3929: URL: https://github.com/apache/logging-log4j2/issues/3929#issuecomment-3308720192
This was observed in a real production application. The application in question makes heavy use of RxJava, where an exception instance propagates forward through some graph of reactive operators, sometimes crossing thread boundaries, and alternately accumulating suppressed exceptions and/or being logged. But as I mentioned in the description, I strongly suspect that parallelism at the application layer is not necessary to trigger this bug. The use of async logging + the attachment of suppressed exceptions close to the site where an exception is logged is likely sufficient. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
