I should qualify that. I would have to look at Ignite’s version of the Log4j2Logger class (I don’t use that myself as it does some things I don’t care for). If it is properly calling the Log4j 2 Configurator with the path you provided then it should be working. However, there are scenarios where it may be initializing Log4j 2 properly but Log4j tried to configure itself first and didn’t find the file but then Ignite forced it to reconfigure with the new file. In that case you can ignore the error message. You should add status=“DEBUG” to the configuration element in your log4j2.xml to see if the file is ever being configured.
Ralph > On Dec 14, 2017, at 11:09 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > Log4j 2 won’t find that because it is config/log4j2.xml and it is looking for > log4j2.xml on the classpath. > > Ralph > >> On Dec 14, 2017, at 11:07 AM, sherryhw <shishuang...@gmail.com> wrote: >> >> It is in "target/classes/config/log4j2.xml" >> Is this what you mentioned? >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> > > >
