[ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2414: ------------------------------------- Hi Amos, I added a couple of comments on your PR as to what I found this morning but I will have to hand it back to you now. It looks like either arquillian or more likely EJB3 remoting inconsistency in WFLY is to blame. {code} WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. Exception in thread "Remoting "endpoint" task-4" java.lang.NoSuchMethodError: org.jboss.logging.Logger.tracef(Ljava/lang/String;I)V at org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:158) at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:386) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} I can see that it is using tracef in master: https://github.com/jbossas/remoting-jmx/blob/master/src/main/java/org/jbo... The thing is when I look in a built version of WFLY it has 3.2.1 in C:\Users\tom\projects\jbosstm\narayana\jboss-as\build\target\wildfly-10.0.0.Alpha2-SNAPSHOT\modules\system\layers\base\org\jboss\logging\main\module.xml and that is the version in the remoting-jmx pom.xml: https://github.com/jbossas/remoting-jmx/blob/master/pom.xml#L154 I think its possible an older incompatible version of jboss-logging could be in the test.war but I can't seem to get Arquillian to leave the war behind to check that out... Tom -- This message was sent by Atlassian JIRA (v6.3.15#6346)