Yavor16 commented on issue #2640:
URL:
https://github.com/apache/logging-log4j2/issues/2640#issuecomment-2152852887
We do it because for every step we create new file + new file appender which
after they are persisted, are deleted. I tried now to create single
LoggerContext instance but t
vy commented on issue #2640:
URL:
https://github.com/apache/logging-log4j2/issues/2640#issuecomment-2152403827
Generating a new `LoggerContext` for every step... seems like pretty much
overkill to me. Why do you do this? Why is simply using the implicitly created
static `LoggerContext` not
Yavor16 commented on issue #2640:
URL:
https://github.com/apache/logging-log4j2/issues/2640#issuecomment-2152369386
We don't have configuration file. Our app mainly uses Spring + Flowable. The
spring version is 5.3.34 and flowable 6.8.0. We generate new LoggerContext for
every step, so we
vy commented on issue #2640:
URL:
https://github.com/apache/logging-log4j2/issues/2640#issuecomment-2152264833
@Yavor16, could you provide a little bit more context, please?
* Could you share your Log4j configuration file, i.e., `log4j2.xml`?
* What kind of an application is this?
vy opened a new pull request, #2645:
URL: https://github.com/apache/logging-log4j2/pull/2645
Fixes #2527.
--
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-
github-actions[bot] merged PR #2644:
URL: https://github.com/apache/logging-log4j2/pull/2644
--
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: notificatio
