Hi, Please note that I found a solution to it by adding this system variable :
-Dlog4j2.loggerContextFactory="org.apache.logging.log4j.core.impl.Log4jContextFactory" Using this property overrides the loading of the jar I mentioned. Thanks, Guy From: Guy Turkenits Sent: Tuesday, January 28, 2020 9:23 AM To: user@geode.apache.org Subject: RE: geode 1.4 problem when log4j-to-slf4j-2.10.0.jar is in the classpath The error occurred in the client side, when trying to call to geode server From: Guy Turkenits Sent: Tuesday, January 28, 2020 9:16 AM To: user@geode.apache.org<mailto:user@geode.apache.org> Subject: geode 1.4 problem when log4j-to-slf4j-2.10.0.jar is in the classpath Hi team, When adding the log4j-to-slf4j-2.10.0.jar to the classpath, I am getting the following error in geode, when removing it all work fine. Caused by: java.lang.ClassCastException: org.apache.logging.slf4j.SLF4JLogger cannot be cast to org.apache.logging.log4j.core.Logger at org.apache.geode.internal.logging.LogService.init(LogService.java:82) at org.apache.geode.internal.logging.LogService.<clinit>(LogService.java:73) The problem that I cant control the classpath and I am getting this jar inside it, do you know how can I overcome this issue when this jar is in the classpath? Thanks, Guy This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service>
