Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10560

JBossWS Native tests intermittent failures with JDK 7

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • EAP_EWP 5.3.0.ER3
    • EAP_EWP 5.2.0 ER6
    • Web Services
    • None
    • Not Required
    • NEW

    Description

      Failures on Sun JDK 7 + OpenJDK 7:

      org.jboss.test.ws.jaxws.jbws1702.JBWS1702TestCase.testInheritanceBare

      javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Cannot find child element: {http://jbws1702.jaxws.ws.test.jboss.org/}getClassCAsClassBResponse
	at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:311)
	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:244)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:171)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:157)
	at $Proxy301.getClassCAsClassB(Unknown Source)
	at org.jboss.test.ws.jaxws.jbws1702.JBWS1702TestCase.testInheritanceBare(JBWS1702TestCase.java:67)
Caused by: org.jboss.ws.WSException: Cannot find child element: {http://jbws1702.jaxws.ws.test.jboss.org/}getClassCAsClassBResponse
	at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:949)
	at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:629)
	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:396)
	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:232)
	... 33 more

      org.jboss.test.ws.tools.JavaToWSDL11TestCase.testComplexTypes
      long message, returned XML does not equal to expected XML, for details see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP5/view/JBossWS/job/eap-5x-jbossws-native-JBM-ibm-openjdk/3/jdk=openjdk-1.7.0-local,label=RHEL5_x86_64/testReport/org.jboss.test.ws.tools/JavaToWSDL11TestCase/testComplexTypes/

      org.jboss.test.ws.jaxrpc.samples.dynamichandler.DynamicHandlerTestCase.testStaticHandlers

      expected:<InitalMessage|[ClientRequest|ServerRequest|ServerResponse|Client]Response> 
  but was:<InitalMessage|[ServerRequest|Server]Response>

      org.jboss.test.ws.jaxrpc.encoded.href.MarshallTestCase.testByteArrayTest

      expected:<H[ello World!]> but was:<H[refEncodedResponse]>

      Details can be found on Jenkins, just search for one of these 4 failures
      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP5/view/JBossWS/job/eap-5x-jbossws-native-JBM-ibm-openjdk/3/testReport/
      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP5/view/JBossWS/job/eap-5x-jbossws-native-JBM-sunjdk/3/testReport/
      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP5/view/JBossWS/job/eap-5x-jbossws-native-JBM-win/3/testReport/
      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP5/view/JBossWS/job/eap-5x-jbossws-native-HQ-ibm-openjdk/3/testReport/
      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP5/view/JBossWS/job/eap-5x-jbossws-native-HQ-sunjdk/3/testReport/
      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP5/view/JBossWS/job/eap-5x-jbossws-smoke-native/11/testReport/

      Attachments

        Issue Links

          incorporates

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBWS-3764 MarshallTestCase leaks

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBWS-3760 DynamicHandlerTestCase result depends on test execution order

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              rsvoboda@redhat.com Rostislav Svoboda
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: