You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Ron Smits (JIRA)" <ji...@apache.org> on 2015/05/12 14:38:59 UTC
[jira] [Created] (MTOMCAT-298) Classloader linkage problem
Ron Smits created MTOMCAT-298:
---------------------------------
Summary: Classloader linkage problem
Key: MTOMCAT-298
URL: https://issues.apache.org/jira/browse/MTOMCAT-298
Project: Apache Tomcat Maven Plugin
Issue Type: Bug
Components: tomcat7
Affects Versions: 2.2
Reporter: Ron Smits
Assignee: Olivier Lamy (*$^¨%`£)
We run 4 war's in a tomcat7:run environment. All wars log using slf4j. In the production environment we have logback-classic and logback-core jar added to the $CATALINA_HOME/lib directory and the configuration in $CATALINA_HOME/conf/logback. This works.
When I do not add extra jars to mvn tomcat7:run environment there is no logging at all.
when I add the logback jars I get a linkage error:
{noformat}
Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class,
org/slf4j/LoggerFactory, and the class loader (instance of org/codehaus/plexus/classworlds/realm/ClassRealm) for resolved class,
org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type org/slf4j/ILoggerFactory used in the signature
{noformat}
(linebreaks added for readability)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org