Open banovp opened 4 years ago
@banovp here is how we solved it on our side, maybe it will help in your case too https://github.com/GluuFederation/oxauth-config/issues/165#issuecomment-691041339
I fight the same issue. Do we have an update on this? Until a proper fix we will remain on version 1.6.x of quarkus (unfortunately the provided workourd doesn't seem to be working on our side)
@rolandhaas I think it's something specific to log4j itself (independent of Quarkus), see this stackoverflow question. Best exclude log4j dependency and use Quarkus' blessed log4j dependency.
Describe the bug
Hi Quarkus Team, we have legacy app migrated and refactored in quarkus. We have some tight dependencies and special configurations for log4j, therefore we've migrated it's usage as well. Since 1.7.0 we are not able to use log4j any more and are getting the exception:
we are using log4j-core in version 2.13.3
if custom json format would be possible, than we could migrate to jboss logging.
https://github.com/quarkusio/quarkus/issues/7451
But we also need to filter the max length of the log lines (because of aws fargate v. 1.4.0, which have issues with the length), which is actually with the logging mechanism of quarkus not possible.
Expected behavior log4j should be usable also instead of quarkus logging
Actual behavior only quarkus logging is possible
To Reproduce Steps to reproduce the behavior:
Configuration
Screenshots n.a.
Environment (please complete the following information): n.a. quarkus since 1.7.0
Additional context n.a.