It's what I said: the main doesn't use pax-logging (as pax-logging is
loaded as bundle later), so it uses only part of the
org.ops4j.pax.logging.cfg content.
Actually, it use only the appender:
private static final String LOG4J_APPENDER_FILE = "log4j.appender.out.file";
...
String getLogFilePath() {
String filename = configProps == null ? null :
configProps.getProperty(KARAF_BOOTSTRAP_LOG);
if (filename != null) {
return filename;
}
Properties props = loadPaxLoggingConfig();
// Make a best effort to log to the default file
appender configured for log4j
return props.getProperty(LOG4J_APPENDER_FILE,
"${karaf.data}/log/karaf.log");
}
Basically, it doesn't deal with the log level.
I will create a Jira to allows to deal with log level (at least for
org.apache.karaf.main logger).
Regards
JB
On 05/06/2015 08:04 PM, sditlinger wrote:
If I change the log file name in the org.ops4j.pax.logging.cfg file, it does
change file where stuff gets logged, so the cfg file is being read. Just
seems like some of the properties from cfg file are being ignored.
e.g. log4j.appender.out.file=${karaf.data}/log/other.log changes the
actual log file name
--
View this message in context:
http://karaf.922171.n3.nabble.com/Loggin-in-cluster-can-t-be-configured-tp4040207p4040214.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
