Re: monitorInterval not working in tomcat

2017-12-03 Thread Remko Popma
Enric, You should be able to remove Log4j-1.2.14 after adding log4j-1.2-api-2.6.2.jar (or log4j-1.2-api-2.4.jar). They provide the same API to the application. The difference is that log4j-1.2-api-2.x.jar uses log4j-core-2.x as its implementation, which is what you want. (Shameless plug)

Re: monitorInterval not working in tomcat

2017-12-03 Thread Enric Jaen
i cannot remove log4j-1.2 because we depend on 3rd lib that uses them. That's why we have bridge to log4j2. I downgraded all to 2.4 but not working autoreload. Enric En domingo, 3 de diciembre de 2017 16:24:23 GMT, Mikael Ståldal escribió: First, remove

Re: monitorInterval not working in tomcat

2017-12-03 Thread Mikael Ståldal
First, remove log4j-1.2.14.jar from classpath. Then make sure you use the same version of all Log4J 2.x jars, now you are mixing 2.4 with 2.6.2. On 2017-12-03 17:07, Enric Jaen wrote: log4j2 is working fine, but not the auto reload. I have tried several configurations but none has worked.

monitorInterval not working in tomcat

2017-12-03 Thread Enric Jaen
log4j2 is working fine, but not the auto reload. I have tried several configurations but none has worked. This is the latest I tried: *** log4j2.xml : *** web.xml (sevlet 3.0)     log4jConfiguration     file:///tmp/log4j2.xml log4j.refresh.interval 5