We are migrating from jboss 4.0.5.ga to jboss 4.2.0.ga Currently working on our development machines (win xp) running on jdk 1.5. We have a remote ejb3 client that could successfully connect to the server when the application is hosted on 4.0.5. We have updated the libraries used by the remote client to connect to the server to use the jars shipped with jboss 4.2.0. When the client attempts to connect to the 4.2.0 server we get the stack trace:Error creating Epic Metadata Connector: java.lang.NoSuchFieldError: | TRACE | java.lang.NoSuchFieldError: TRACE | at | org.jboss.logging.Log4jLoggerPlugin.isTraceEnabled(Log4jLoggerPlugin.jav | a:85) | at org.jboss.logging.Logger.isTraceEnabled(Logger.java:122) | at | org.jboss.security.SecurityAssociation.<clinit>(SecurityAssociation.java | :145) I've had a look at the log4j.properties included in the jboss client jar (the only log4j config on the client) and there is no mention of a trace level... Anyone got any idea what might be going on? Thanks, Andy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050046#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...