Closed RobertFloor closed 9 months ago
We could prevent is if we add this filter to our log4j config file, but it needs to stay there every run:
appender.console.filter.1.type = RegexFilter
appender.console.filter.1.regex = .*221082.*
appender.console.filter.1.onMatch = DENY
appender.console.filter.1.onMismatch = NEUTRAL
The issue is being evaluated upstream; in any case can you check if the merged PR above fixes your issue in the collection?
yes it fixes our problem
SUMMARY
The artemis mask command writes additional output when other jars are present in the lib folder, such as the prometheus jar. This creates a misconfiguration. Perhaps it is a problem in the upstream version?
ISSUE TYPE
ANSIBLE VERSION
COLLECTION VERSION
STEPS TO REPRODUCE
This works
But logging ends up in the artemis.users file
The logging suggests there is a problem with ArtemisPrometheusMetricsPlugin. When I remove this from the broker.xml
I get a password mask command without logging
EXPECTED RESULTS
Get not additional login when running artemis amsk command
ACTUAL RESULTS