You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/06/07 10:34:25 UTC

[jira] Resolved: (DIRMINA-348) slf4j InvalidClassChangeError - No diagnostics

     [ https://issues.apache.org/jira/browse/DIRMINA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee resolved DIRMINA-348.
---------------------------------

    Resolution: Fixed

We documented recommended version of SLF4J library.

http://mina.apache.org/quick-start-guide.html

and added FAQ entry.

http://mina.apache.org/faq.html (might take some time my change is applied.)


> slf4j InvalidClassChangeError - No diagnostics
> ----------------------------------------------
>
>                 Key: DIRMINA-348
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-348
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.1
>         Environment: $ java -version
> java version "1.5.0_06"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-113)
> Java HotSpot(TM) Client VM (build 1.5.0_06-68, mixed mode, sharing)
> $ uname -a
> Darwin gr8.config 8.8.2 Darwin Kernel Version 8.8.2: Thu Sep 28 20:43:26 PDT 2006; root:xnu-792.14.14.obj~1/RELEASE_I386 i386 i386
>            Reporter: Ben Hood
>            Priority: Minor
>
> Not having the correct slf4j plugin for the log library you use in a project causes an InvalidClassChangeError.
> This manifests itself in the
> private void fireEvent( NextFilter nextFilter, IoSession session, EventType type, Object data )
> method when the first time the logger instance has a method invoked on it.
> The solution is to get the correct plugin on the classpath, e.g. by adding this to your pom:
> <dependency>
>             <groupId>org.slf4j</groupId>
>             <artifactId>slf4j-log4j12</artifactId>
>             <version>1.2</version>
>             <scope>runtime</scope>
>         </dependency>
> It would be nice to somehow log this error at least somehow to std err, because the error was being swallowed without any diagnostics being output.
> This costs a lot of time and may lead to people not using mina because of a trivial issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.