-
Bug
-
Resolution: Done
-
Major
-
JDG 7.1.0 ER1
-
None
-
-
-
-
-
-
ER3
JWS Session Externalization library has its own jboss logging jar, which can conflict with default jboss logging included in JWS/Tomcat 8. In most cases works fine, conflicts appears only in some cases, e.g. when HotRod client want to log exception (and in such case it hides orginal root cause of the exception), e.g. :
Caused by: java.lang.NoSuchMethodError: org.infinispan.client.hotrod.logging.Log.tracef(Ljava/lang/Throwable;Ljava/lang/String;II)V at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.logTransportErrorAndThrowExceptionIfNeeded(RetryOnFailureOperation.java:134) at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:61) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.ping(RemoteCacheImpl.java:673) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.resolveCompatibility(RemoteCacheImpl.java:734) at org.infinispan.client.hotrod.RemoteCacheManager.createRemoteCache(RemoteCacheManager.java:666) at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:552) at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:547) at org.wildfly.clustering.web.hotrod.session.HotRodSessionManagerFactoryConfiguration.getCache(HotRodSessionManagerFactoryConfiguration.java:37) at org.wildfly.clustering.web.hotrod.session.HotRodSessionManagerFactory.createSessionFactory(HotRodSessionManagerFactory.java:76) at org.wildfly.clustering.web.hotrod.session.HotRodSessionManagerFactory.createSessionManager(HotRodSessionManagerFactory.java:72) at org.wildfly.clustering.tomcat.hotrod.HotRodManager.startInternal(HotRodManager.java:213) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 12 more
- is related to
-
JDG-424 Debug/Trace logging fails in library mode on EAP 6
- Closed