directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRAPI-138) java.lang.LinkageError: loader constraint violation:
Date Thu, 20 Jun 2013 13:12:20 GMT

    [ https://issues.apache.org/jira/browse/DIRAPI-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689225#comment-13689225
] 

Emmanuel Lecharny commented on DIRAPI-138:
------------------------------------------

See if it's related to the pb in http://code.google.com/p/myschedule/issues/detail?id=35
                
> java.lang.LinkageError: loader constraint violation:
> ----------------------------------------------------
>
>                 Key: DIRAPI-138
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-138
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M17
>         Environment: x64 linux, Atlassian Jira SDK, Spring, OSGi, Maven
>            Reporter: Ragnar Skulason
>            Priority: Critical
>
> I was trying to use Apache Directory LDAP in an jira plugin, but I get this error:
> java.lang.LinkageError: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;"
the class loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5)
of the current class, org/slf4j/LoggerFactory, and the class loader (instance of org/apache/catalina/loader/WebappClassLoader)
for resolved class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for the
type org/slf4j/ILoggerFactory used in the signature
> 	at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:299)
> 	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269)
> 	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
> 	at org.apache.mina.core.service.IoHandlerAdapter.<clinit>(IoHandlerAdapter.java:35)
> 	at com.consultingtoolsmiths.jira.samples.webwork.ActionAlpha.getLdapConnection(ActionAlpha.java:134)
> 	at com.consultingtoolsmiths.jira.samples.webwork.ActionAlpha.doDefault(ActionAlpha.java:159)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70)
> 	at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56)
> 	at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:433)
> 	at webwork.action.ActionSupport.execute(ActionSupport.java:157)
> 	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:85)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message