Open ex3ndr opened 8 years ago
Right. It's probably best to drop the log4j binary dependency and just have the logging backend open in some back-compatible way.
log4j sounds like some friendly old ghost :-) -- its been a long time since I gave it any thought.
I thought we removed the log4j dependency at some point (the default logger is log4j but IIRC, we removed that dependency.)
Ranga.
From: vladimirralev notifications@github.com Sent: Sunday, August 21, 2016 4:23:42 PM To: usnistgov/jsip Subject: Re: [usnistgov/jsip] Log4J Upgrade (#6)
Right. It's probably best to drop the log4j binary dependency and just have the logging backend open in some back-compatible way.
You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/usnistgov/jsip/issues/6#issuecomment-241279680, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHNZkAVNOoDi5uFhMs5fF0wCWaT8wDgeks5qiLPOgaJpZM4JpJYu.
I think slf4j is the best choice. http://www.slf4j.org
one request, please make debug and server logs rollable. I see debug log file size growing to GBs if I keep the debug level under heavy load.
I have upgraded my application to latest Log4J 2.x and observed that, sip stack still logs messages to debug and server log files but without considering logging format defined by log4J 2.x log config file. Looks like, some compliance issues.
Thanks, Ganesh
Hey!
log4j 1.2 is already reached end-of-life and isn't jsip should be updated to log4j 2?
Thanks.