Hide Forgot
Date of First Response: 2008-01-14 11:54:02 project_key: SOA See http://hudson.qa.jboss.com/hudson/view/SOA/job/jboss-soa-platform-WS-testsuite/51/testReport/(TESTS-TestSuites/ There are 15 tests failing. Most of them are because tests are not picking up authentication properties correctly. One could more likely be a real issue: testSOAPMessageToEndpointQueue java.lang.NoClassDefFoundError: org/jboss/aop/pointcut/PointcutStats at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.<clinit>(ClientConnectionFactoryDelegate.java) at sun.misc.Unsafe.ensureClassInitialized(Native Method) at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917) at java.lang.reflect.Field.getFieldAccessor(Field.java:898) at java.lang.reflect.Field.getLong(Field.java:527) at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1586) at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:52) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:408) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:400) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:297) at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:531) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at java.rmi.MarshalledObject.get(MarshalledObject.java:135) at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:72) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:654) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.test.ws.jaxrpc.samples.jmstransport.JMSTransportTestCase.testSOAPMessageToEndpointQueue(JMSTransportTestCase.java:76) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23)
Link: Added: This issue depends JBWS-1946
Link: Added: This issue is related to JBQA-1003
Len, assigning to you again. Probably componets need to have someone assigned by default. The dependency JBWS issue doesn't have an assignee as well.
Len, please see the associated issue, which IMO duplicates this one. Rajesh should be able to explain the required changes or if necessary confirm that this test can be exclude when JBM is in place. So far all the JMS tests have been run against JBossMQ, AFAIK.
Link: Added: This issue is related to JBPAPP-491
The changes required for this are simple, please see the attached JBWS issue. I'm still not sure why this was in the JBWS repository nor why it was assigned to me.
Are we not going to have a WS CP branch?
JBWS-1987 a test suite failure running on windows (linux looks fine)
Link: Added: This issue depends JBWS-1987
Link: Added: This issue is a dependency of JBWS-2121
Link: Removed: This issue is a dependency of JBWS-2121
Link: Added: This issue is related to JBWS-2121
Link: Added: This issue depends JBWS-2245
Link: Added: This issue depends JBPAPP-1194
JBWS-1987 is still there: http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-ws-os-jdk15/19/label=Win2k3_x86_64_res/testReport/org.jboss.test.ws.jaxws.jbws1666/JBWS1666TestCase/testClientAccess/ Should the issue be reopened? Or could it be that the change didn't make it downstream to SOA-P 4.3 CR1?
These errors are harmless IMO, but I can't think of a reliable way to track them between releases. Len, any ideas? Should we start wiki pages with notes about every release because JIRA seems not the best tool IMO as well testify is too official sometimes.
AFAIK Lukas, you are running these tests. Can you answer Len's question?
Hey Lukas - did this test run yet for 43 CP01? Thx!
Yes, some of the WS tests have already run. I am seeing the same issues as always plus possibly a new one which I yet need to investigate. The "old" issues are there at least since I've started maintaining these tests inside SOA.
Can we review these on Monday - and either open up new JIRAs as needed or decide to not press for fixes. Do you have a URL for the test results? Thanks!
I think that this can be resolved - JBossWS tests are taken care of, they are run with every new build and the results are reported.