Skip to:
Adding -Dlog4j2.formatMsgNoLookups=true to the environment setup of okapi in the debian/ubuntu package fixed the log4j issue:
https://github.com/julianladisch/okapi/blob/master/.github/workflows/log4j-debian.yml
Successful run:https://github.com/julianladisch/okapi/runs/4504598357?check_suite_focus=true
We know that Log4j 2.15.0 is not a complete fix: https://issues.apache.org/jira/browse/LOG4J2-3208
Using only -Dlog4j2.formatMsgNoLookups=true fixed the issue for okapi 4.9.0-1 debian/ubuntu package.
Adding the option has no disadvantages.
But it is an additional lock if anything goes wrong, for example if there is some strange dependency.
We can remove this options when Okapi has updated to the log4j version with the LOG4J2-3208 fix and we are sure that we don't need it.
please clarify on this ticket why we need this in addition to , thanks.
Adding -Dlog4j2.formatMsgNoLookups=true to the environment setup of okapi in the debian/ubuntu package fixed the log4j issue:
https://github.com/julianladisch/okapi/blob/master/.github/workflows/log4j-debian.yml
Successful run:
https://github.com/julianladisch/okapi/runs/4504598357?check_suite_focus=true