That’s a good summary, thanks. For people who do use log4j2 with Ignite, this
is the best public summary I’ve seen so far:
https://www.gridgain.com/resources/blog/what-you-need-know-about-log4j-vulnerabilities-apache-ignite-and-gridgain
In summary, there are immediate mitigations you can apply a
So far I haven't seen anyone ask about the issue here in the lists. So I'll
give it a go.
I'm personally using 2.8.1
1- If we are running as a service using .DEB or .RPM or other linux
packages: The default logging is JUL so nothing to worry about.
2- If we aren' t specifically enabling the ignit
