Is org.jboss.logging.Logger in JBoss 4.2.1 compatible with S

[tonylmai]

Hello all,

I am running into weird logger incompatible version after upgrading my JBoss AS to JBoss 4.2.1GA (from 4.0.5GA). I am still using Seam 1.2.1GA. No change in my code.

Yet my client is now complaining that it could not perform a Context.lookup(). It threw an exception at:

java.lang.NoSuchFieldError: TRACE
at org.jboss.logging.Log4jLoggerPlugin.isTraceEnabled(Log4jLoggerPlugin.java:85)
at org.jboss.logging.Logger.isTraceEnabled(Logger.java:122)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:620)

So somewhere in the server/client, a wrong version of Logger is being used and I don't know which component is loading this Logger in the first place.

Has anyone here run into this problem or know how to fix this. I would appreciate a comment.

Thanks
-tony

[gavin.king]

This looks like a bug that was already fixed in Seam, but I did not think that the bug was in Seam 1.2.1. Are you sure you are really using 1.2.1.

Anyway, it can be solved by upgrading to a more recent log4j.

[tonylmai]

I am using Seam 1.2.1GA

12:29:06,046 INFO [ServletContextListener] Welcome to Seam 1.2.1

I dropped in the latest log4j.jar from JBoss 4.2.1GA build in front of the client's classpath. Made no differences.

I am starting to doubt if it's Seam at all since I have Seam's component performing multiple Context.lookup() to get to the backend components. They were done within the same server whereas my client attempted to connect from a separate JVM.

Not sure how to proceed however.

Thanks Gavin
-tony

[gavin.king]

It has to be something to do with a bad log4j.jar version somewhere.