Hi Dharam, In general this may be possible by excluding log4j from your classpath and instead bringing in the log4j-over-slf4j module (http://www.slf4j.org/legacy.html#log4j-over-slf4j <http://www.slf4j.org/legacy.html#log4j-over-slf4j>). However, this bridge does not support log4j appenders or filters - and I believe that Geode does make use of those features.
> On Dec 5, 2016, at 9:18 PM, Dharam Thacker <[email protected]> wrote: > > Hi Team, > > We have a common logback thread based logging configuration across all > distributed application components. > > We use slf4j abstraction for all our logging needs. > > Geode internally uses Apache log4j 2 implementation. Is there any way, I can > route log4j messages so that it also goes via slf4j and internally logback? > > Thanks & Regards, > - Dharam Thacker
