For some reason, my application programmatically reconfigures log4j (in some cases), namely user add-ons. However, changes are lost as soon as someone manually edits the log4j configuration file.
How to make sure that our programmatic changes to the log4j configuration are not lost? Or how to get notification when reconfiguring log4j?
The application runs on JBoss, and the problem occurs when its file is $JBOSS/server/default/conf/jboss-log4j.xmledited, but I believe that the problem is not specific to JBoss AS at all.
source
share