project_key: JBPAPP6 Hi Alessio. I noticed JBWS3140 test failures in some of my jobs. It happened only with Oracle JDK 7 64-bit and on some 64bit machines. When I executed JBWS3140 tests manually on the same machines, it passed + I couldn't simulate JBWS3140 failures on my local 64-bit machine. I just want to track it and let you know. Not reported as a bug but only as possible QA risk. >>> org.jboss.test.ws.jaxws.jbws3140.JBWS3140AddrResponsesTestCase.testWsaResponses >>> org.jboss.test.ws.jaxws.jbws3140.JBWS3140MtomAddrFeatureTestCase.testMtomSmall https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/jdk=java17_default,label=RHEL6_x86_64/ https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-solaris/jdk=java17_default,label=sol10_sparc64/ https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-windows/jdk=java17_default,label=Win2k8_x86_64/
Link: Added: This issue relates to AS7-2166
Link: Added: This issue is related to JBPAPP-7965
It happened with some runs on DR10 and DR12 too.
TestCase contains now (in EAP 6.0.0 ER1 and JBossWS CXF 4.0.1) more details, see: http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-windows/18/jdk=java17_default,label=dev99-W2k8r2-x86_64/testReport/org.jboss.test.ws.jaxws.jbws3140/JBWS3140AddrResponsesTestCase/testWsaResponses/ http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-windows/18/jdk=java17_default,label=dev99-W2k8r2-x86_64/testReport/org.jboss.test.ws.jaxws.jbws3140/JBWS3140MtomAddrFeatureTestCase/testMtomSmall/ http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/jdk=java17_default,label=RHEL6_i386/10/testReport/org.jboss.test.ws.jaxws.jbws3140/JBWS3140AddrResponsesTestCase/testWsaResponses/ http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/jdk=java17_default,label=RHEL6_i386/10/testReport/org.jboss.test.ws.jaxws.jbws3140/JBWS3140MtomAddrFeatureTestCase/testMtomSmall/
The same problem happened with OpenJDK7 on RHEL6 too, but only in 1 run. Error message says: SOAPFaultException is expected but received: java.lang.NullPointerException at org.jboss.test.ws.jaxws.jbws3140.ServletTestClient.doMtom(ServletTestClient.java:86) http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/jdk=openjdk-1.7.0-local,label=RHEL6_i386/12/testReport/
Hi Rotislav, I can't reproduce this locally (tried multiple times) with OpenJDK 1.7.0-b146, current AS7 master and current JBossWS-CXF 4.0.x EAP6 branch. Can you please check if we can have fresher results from hudson (using latest EAP6 & ws stack)?
With ER3 build you can see these failures in: https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-solaris/12/jdk=java17_default,label=sol10_x86_64/testReport/ https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-solaris/12/jdk=java17_default,label=sol11_x86_64/testReport/ https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-windows/19/jdk=java17_default,label=dev99-W2k8r2-x86_64/testReport/ https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-windows/20/jdk=java17_default,label=dev96-W2k8-x86/ https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/12/jdk=openjdk-1.7.0-local,label=RHEL6_i386/testReport/ https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/12/jdk=java17_default,label=RHEL6_i386/testReport/ https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/12/jdk=java17_default,label=RHEL6_x86_64/testReport/ For ER5 I didn't run WS testsuite, I'm planning to do so with ER6.
Link: Added: This issue is a dependency of JBPAPP-8827
Link: Removed: This issue is a dependency of JBPAPP-8827
I could find these failures with EAP 6.0.0 ER6 (JBossWS 4.0.3) NPE was thrown, failures are not 100% reproducible. See https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/jdk=java17_default,label=RHEL6_x86_64/17/consoleText and search for 'Running org.jboss.test.ws.jaxws.jbws3140.JBWS3140' {code} 03:46:22,089 INFO [org.jboss.as.server] (management-handler-thread - 6) JBAS018559: Deployed "jbws3140-client.war" 03:46:22,135 ERROR [stderr] (http--127.0.0.1-8080-6) ServletClient:init() Exception: javax.naming.NamingException: org.jboss.wsf.spi.WSFException: Cannot create service [Root exception is java.lang.RuntimeException: org.jboss.wsf.spi.WSFException: Cannot create service] 03:46:22,139 ERROR [stderr] (http--127.0.0.1-8080-6) javax.naming.NamingException: org.jboss.wsf.spi.WSFException: Cannot create service [Root exception is java.lang.RuntimeException: org.jboss.wsf.spi.WSFException: Cannot create service] 03:46:22,142 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135) 03:46:22,144 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) 03:46:22,146 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) 03:46:22,148 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:123) 03:46:22,149 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) 03:46:22,150 ERROR [stderr] (http--127.0.0.1-8080-6) at javax.naming.InitialContext.lookup(InitialContext.java:411) 03:46:22,151 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.test.ws.jaxws.jbws3140.ServletTestClient.init(ServletTestClient.java:49) 03:46:22,153 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1202) 03:46:22,154 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:952) 03:46:22,155 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:188) 03:46:22,157 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) 03:46:22,159 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) 03:46:22,161 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) 03:46:22,162 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 03:46:22,163 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 03:46:22,165 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) 03:46:22,166 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) 03:46:22,167 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) 03:46:22,168 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) 03:46:22,170 ERROR [stderr] (http--127.0.0.1-8080-6) at java.lang.Thread.run(Thread.java:722) 03:46:22,171 ERROR [stderr] (http--127.0.0.1-8080-6) Caused by: java.lang.RuntimeException: org.jboss.wsf.spi.WSFException: Cannot create service 03:46:22,174 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.webservices.webserviceref.WSRefValueSource.getValue(WSRefValueSource.java:77) 03:46:22,176 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.naming.ValueManagedReferenceFactory.getReference(ValueManagedReferenceFactory.java:49) 03:46:22,177 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:133) 03:46:22,179 ERROR [stderr] (http--127.0.0.1-8080-6) ... 19 more 03:46:22,180 ERROR [stderr] (http--127.0.0.1-8080-6) Caused by: org.jboss.wsf.spi.WSFException: Cannot create service 03:46:22,181 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.wsf.spi.WSFException.rethrow(WSFException.java:55) 03:46:22,182 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.ws.common.serviceref.AbstractServiceObjectFactoryJAXWS.getObjectInstance(AbstractServiceObjectFactoryJAXWS.java:123) 03:46:22,183 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.as.webservices.webserviceref.WSRefValueSource.getValue(WSRefValueSource.java:75) 03:46:22,185 ERROR [stderr] (http--127.0.0.1-8080-6) ... 21 more 03:46:22,186 ERROR [stderr] (http--127.0.0.1-8080-6) Caused by: java.lang.reflect.InvocationTargetException 03:46:22,187 ERROR [stderr] (http--127.0.0.1-8080-6) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 03:46:22,188 ERROR [stderr] (http--127.0.0.1-8080-6) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 03:46:22,189 ERROR [stderr] (http--127.0.0.1-8080-6) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 03:46:22,190 ERROR [stderr] (http--127.0.0.1-8080-6) at java.lang.reflect.Method.invoke(Method.java:601) 03:46:22,191 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.ws.common.serviceref.AbstractServiceObjectFactoryJAXWS.instantiatePort(AbstractServiceObjectFactoryJAXWS.java:198) 03:46:22,193 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.ws.common.serviceref.AbstractServiceObjectFactoryJAXWS.getObjectInstance(AbstractServiceObjectFactoryJAXWS.java:111) 03:46:22,194 ERROR [stderr] (http--127.0.0.1-8080-6) ... 22 more 03:46:22,195 ERROR [stderr] (http--127.0.0.1-8080-6) Caused by: javax.xml.ws.WebServiceException: Port {http://TestEndpoint.org}MTOMTestPort2 not found. 03:46:22,196 ERROR [stderr] (http--127.0.0.1-8080-6) at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:328) 03:46:22,197 ERROR [stderr] (http--127.0.0.1-8080-6) at javax.xml.ws.Service.getPort(Service.java:140) 03:46:22,198 ERROR [stderr] (http--127.0.0.1-8080-6) at org.jboss.test.ws.jaxws.jbws3140.EndpointService.getMTOMTestPort2(EndpointService.java:126) 03:46:22,199 ERROR [stderr] (http--127.0.0.1-8080-6) ... 28 morejboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135) {code} Previous run with the same configuration was successful for JBWS3140 testcases: https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/jdk=java17_default,label=RHEL6_x86_64/16/consoleText You can compare logs with run #17. More details: https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/jdk=java17_default,label=RHEL6_x86_64/lastCompletedBuild/testReport/org.jboss.test.ws.jaxws.jbws3140/JBWS3140AddrResponsesTestCase/testWsaResponses/ https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/jdk=java17_default,label=RHEL6_x86_64/lastCompletedBuild/testReport/org.jboss.test.ws.jaxws.jbws3140/JBWS3140MtomAddrFeatureTestCase/testMtomSmall/
Cannot reproduce issue on EAP 6.0.0 ER7, JBossWS 4.0.4 with: [supernova][/home/opalka/svn/jbossws/stack/cxf/branches/jbossws-cxf-4.0.x]>java -version java version "1.7.0_03" Java(TM) SE Runtime Environment (build 1.7.0_03-b04) Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode)
Exactly, as I mentioned failures are not 100% reproducible.
I hit it again (4 times from 21) with ER7: jdk=java17_default,label=RHEL6_x86_64 jdk=openjdk-1.7.0-local,label=RHEL6_i386 https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/lastCompletedBuild/testReport/ jdk=java17_default,label=sol11_sparc64 https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/lastCompletedBuild/testReport/ jdk=java17_default,label=dev97-W2k8-x86_64 https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-windows/lastCompletedBuild/testReport/
I tried to reproduce it again and again no luck. I also reviewed the test and I don't see anything suspicious there. From the stack trace it seems that endpoint in jbws3140-server.war is not available at time when client servlet in jbws3140-client.war is constructing JAXWS client proxy via JNDI lookup to endpoint located in jbws3140-server.war. I'd say test needs to be rewritten to ensure proper servlet & endpoint initialization ordering.
Link: Added: This issue is a dependency of JBPAPP-9188
Link: Removed: This issue is related to JBPAPP-7965
Link: Added: This issue is a dependency of JBPAPP-9438
JBWS3140TestCase issue was spotted again, random failures on JDK7. Testcase end on NPE in ServletTestClient:86, mtomTestPort is not initialized Server log complains: Caused by: javax.xml.ws.WebServiceException: Port {http://TestEndpoint.org}MTOMTestPort2 not found. RHEL results: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/30/testReport/ 4 failures from 10 Solaris results: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-solaris/27/testReport/ 3 failures from 5 Failed Test Log Example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/30/jdk=java17_default,label=RHEL5_x86_64/consoleText Passed Test Log Example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/30/jdk=java17_default,label=RHEL5_x86/consoleText search for "Running org.jboss.test.ws.jaxws.jbws3140.JBWS3140TestCase"
I executed org.jboss.test.ws.jaxws.jbws3140.JBWS3140TestCase manually on hudson machine (dsp01) where it failed. Manual execution of JBWS3140TestCase passed without error. The same version of java as in Hudson job was used. Test failure during automated TS execution can be caused by high load and server is not fast enough to initialize endpoint for client. {code} [hudson@dsp01 shared-tests]$ java -version java version "1.7.0_04" Java(TM) SE Runtime Environment (build 1.7.0_04-b20) Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode) {code}
Question is why it happens only on JDK 7 ? JDK 6 tests are executed on the same machines.
This issue is not a blocker nor a critical for EAP 6.0.1. Thus it is moved to TBD EAP 6 to be triaged for the next EAP 6.x release.
EAP 6.0.1 ER3: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/31/testReport/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-solaris/28/testReport/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-windows/39/testReport/
Docs QE Status: Removed: NEW
EAP 6.0.1 ER4.1: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/32/testReport/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-solaris/29/testReport/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-windows/41/testReport/
Update for EAP 6.1.0 ER2: Failure happens constantly on OpenJDK 7, random failure on Oracle JDK 7. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/33/testReport/
There are known issues with testsuite on JDK7. first fully jdk7 compliant AS codebase is current AS8 commit that enables this is https://github.com/jbossas/jboss-as/commit/a355e54dfa02b514e8031bf3fa1ff206d2619a1e but this ATM cannot be backported to EAP 6.x because it requires javassit version that has known issues at runtime see https://issues.jboss.org/browse/AS7-6637 when javasisst is fixed, we can backport fixes to EAP 6.x so build/testsuite would work also on jdk7
Rosta, can you please try my lastest fix ? https://source.jboss.org/changelog/JBossWS?cs=17389 We wrongly define a non-exsiting portName, it will be loaded transiently with some versionjdk6 and jdk7.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-60-jbossws-testsuite-rhel/34/ - red ball for one node == No space left on device shared testsuite manualy hacked in local repo to reflect #17389 JBWS3140 tests didn't fail
http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/branches/jbossws-shared-testsuite-4.1.x/testsuite/src/test/java/org/jboss/test/ws/jaxws/jbws3140/EndpointService.java doesn't contain fix from #17389 Please back-port your changes to jbossws-shared-testsuite-4.1.x branch. Latest 4.1.2.Final tag doesn't contain fix for this issue.
Merge to 4.x branch - https://source.jboss.org/changelog/JBossWS?cs=17417
Moving to ON_QA based on "Bumped 10 approved bugs to EAP 6.2" email thread in eap-pm list.
Verified on EAP 6.1.1 ER7