Hide Forgot
Date of First Response: 2008-09-22 10:34:20 project_key: SOA For full details, please look at http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-jbm/lastBuild/#showFailuresLink Generally most tests fail stating queues are not in state they need to be. Exceptions like: junit.framework.AssertionFailedError: Message count for queue sourceQueue on server is 229 java.lang.IllegalStateException: Cannot remove references while deliveries are in progress, there are 1 But also: java.lang.NoSuchMethodError: org.jboss.remoting.transport.socket.ServerAddress.<init>(Ljava/lang/String;IZII)V at org.jboss.test.thirdparty.remoting.ServerAddressTest.testEquals(ServerAddressTest.java:40) These errors are not seen when tests run against EAP.
(03:30:48 PM) fox: akostadinov: if you're getting java.lang.NoSuchMethodError: org.jboss.remoting.transport.socket.ServerAddress.<init>(Ljava/lang/String;IZII)V (03:30:48 PM) fox: at org.jboss.test.thirdparty.remoting.ServerAddressTest.testEquals(ServerAddressTest.java:40) (03:31:05 PM) fox: akostadinov: that almost certainly means you're running using an incorrect version of jboss remoting (03:31:16 PM) fox: akostadinov: which would explain your problem (03:32:15 PM) fox: akostadinov: you've compiled against one version and you're running tests using another (probably older) version (03:32:26 PM) akostadinov: fox: cool, that can help, thanks, I'll check
I can't find any differences in jboss-remoting.jar between EAP and SOA-P. Will investigate further tomorrow.
From IRC: <jcoleman> ldimaggi_mtg: If I compile a trivial test against the client jar and run it against the server - boom - same exception ;-( <ldimaggi_mtg> jcoleman, Same exception as in SOA-815? <jcoleman> ldimaggi_mtg: It looks like the class definition is different between client and server.
Changed severity to blocker- this problem be the root cause of the repeated failures being seen by the automated regression test suites.
The version we have in jboss-as/client/jbossall-client.jar is the version that we get from EAP FP01. The versions in jboss-as/server/*/soap.esb/jbossall-client.jar are different versions (but all the same different version). They appear to have an older remoting version within them, that has a different constructor for ServerAddress, which is what causes the runtime exception. There are also other differences.
Link: Added: This issue depends SOA-747
Highly likely SOA-708 is related to this one.
Link: Added: This issue related SOA-708
It seems that the versions of JBoss Remoting is 1) JBM is compiled against 2.2.2SP8 2) It is run against 2.2.2SP9 3) In the wrong JAR file there is 2.2.0SP4
Jiri, is this all coming from EAP FP01 then, as J mentioned?
All failures except one are gone. Actually ther e are some on every build but these are timing related and are not consistent between runs. org.jboss.test.messaging.jms.ManifestTest.testManifestEntries junit.framework.ComparisonFailure: expected:<JBoss Messaging> but was:<UNKNOWN> It is failing consistently. It is *not* present in EAP builds. But we've seen it before as well SOA-547 JBMESSAGING-1287
All failures except one are gone in IR5. Actually there are some on every build but these are timing related and are not consistent between runs. org.jboss.test.messaging.jms.ManifestTest.testManifestEntries junit.framework.ComparisonFailure: expected:<JBoss Messaging> but was:<UNKNOWN> It is failing consistently. It is *not* present in EAP builds. But we've seen it before as well SOA-547 JBMESSAGING-1287 so I don't think it is so critical.
Link: Added: This issue depends JBMESSAGING-1287
Link: Removed: This issue related SOA-708
"3) In the wrong JAR file there is 2.2.0SP4" So do we know where this version comes (came) from?
The JAR with wrong version is no longer present in IR5, so it was probably removed as part of SOA-747