Bug 777761 (SOA-277)

Summary:	JBoss WS unit tests against SOA-P
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Aleksandar Kostadinov <akostadinov>
Component:	JBossWS	Assignee:	Lukáš Petrovický <lpetrovi>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 Beta 1	CC:	kevin.conner, lpetrovi
Target Milestone:	---
Target Release:	CONTINUING
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-277
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-31 08:44:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Aleksandar Kostadinov 2008-01-05 06:13:47 UTC

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)

Comment 1 Aleksandar Kostadinov 2008-01-05 06:28:12 UTC

Link: Added: This issue depends JBWS-1946

Comment 2 Aleksandar Kostadinov 2008-01-05 06:29:51 UTC

Link: Added: This issue is related to JBQA-1003

Comment 3 Aleksandar Kostadinov 2008-01-05 06:31:41 UTC

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.

Comment 4 Heiko Braun 2008-01-14 16:54:02 UTC

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.

Comment 5 Heiko Braun 2008-01-14 16:54:02 UTC

Link: Added: This issue is related to JBPAPP-491

Comment 6 Kevin Conner 2008-01-15 12:53:10 UTC

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.

Comment 7 Aleksandar Kostadinov 2008-02-07 07:24:18 UTC

Are we not going to have a WS CP branch?

Comment 8 Aleksandar Kostadinov 2008-02-07 15:25:14 UTC

JBWS-1987 a test suite failure running on windows (linux looks fine)

Comment 9 Aleksandar Kostadinov 2008-02-07 15:25:14 UTC

Link: Added: This issue depends JBWS-1987

Comment 10 Thomas Diesler 2008-04-09 15:11:48 UTC

Link: Added: This issue is a dependency of JBWS-2121

Comment 11 Thomas Diesler 2008-04-09 15:12:10 UTC

Link: Removed: This issue is a dependency of JBWS-2121

Comment 12 Thomas Diesler 2008-04-09 15:12:32 UTC

Link: Added: This issue is related to JBWS-2121

Comment 13 Aleksandar Kostadinov 2008-07-01 15:05:01 UTC

Link: Added: This issue depends JBWS-2245

Comment 14 Magesh Bojan 2008-09-27 05:46:20 UTC

Link: Added: This issue depends JBPAPP-1194

Comment 15 Lukáš Petrovický 2008-10-20 10:02:20 UTC

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?

Comment 16 Aleksandar Kostadinov 2008-10-21 14:55:45 UTC

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.

Comment 19 Aleksandar Kostadinov 2009-02-18 14:30:17 UTC

AFAIK Lukas, you are running these tests. Can you answer Len's question?

Comment 20 Len DiMaggio 2009-02-19 01:31:29 UTC

Hey Lukas - did this test run yet for 43 CP01? Thx!

Comment 21 Lukáš Petrovický 2009-02-20 07:10:31 UTC

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.

Comment 22 Len DiMaggio 2009-02-20 21:29:00 UTC

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!

Comment 23 Lukáš Petrovický 2009-07-02 12:47:39 UTC

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.