org.jnp.interfaces.NamingContext throwing java.lang.NoSuchFi

[tonylmai]

Hello all,

I am using JBoss 4.2.1GA. When I tried to perform a Context.lookup(), I ran into a java.lang.NoSuchFieldError: TRACE exception in the following line:

org.jnp.interfaces.NamingContext:622
 boolean trace = log.isTraceEnabled();

where log is of type org.jboss.logging.Logger.class.

I think it's my client using the wrong jar file. I can see that there are several Logger in the following jar files:

jboss-common-client.jar
jbossall-client.jar
jboss-common.jar
jboss-ejb3-all.jar

Which jar should I use?

Thanks

[dimitris]

Have you somehow mixed libraries from a previous JBoss or EJB3 version? What's your exact usecase?

[tonylmai]

I am upgrading from JBoss 4.0.5GA to 4.2.1.GA. I am also using Seam 1.2.1GA.

The server came up fine. It's the client that I am trying to bring up that threw this exception. My client references all the jar files reside in the jboss-4.2.1.GA\client directory. Perhaps these jars conflict with each other?

Do you know the minimal set of jar files I need if I only do EJB + JSF?

Thanks
-tony

[tonylmai]

I still run into the same exception when my client referenced only jbossall-client.jar.

Help please.

Thanks
-tony

[tonylmai]

I think someone else also had this problem.

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049229#4049229

[titone95]

I've updated log4j (1.2.14) and it works.