Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8139

VDX - pretty print gives different message on IBM JDK than on Oracle/OpenJDK for incorrect value of element or unexpected empty element

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.DR11
    • 7.1.0.DR10
    • Management
    • None

    Description

      VDX - pretty print gives different message on IBM JDK than on Oracle/OpenJDK for incorrect value of element or unexpected empty element

      IBM JDK details:
      java version "1.8.0"
      Java(TM) SE Runtime Environment (build pxa6480sr3fp20-20161019_02(SR3 FP20))
      IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20161013_322271 (JIT enabled, AOT enabled)
      J9VM - R28_Java8_SR3_20161013_1635_B322271
      JIT - tr.r14.java.green_20161011_125790
      GC - R28_Java8_SR3_20161013_1635_B322271_CMPRSS
      J9CL - 20161013_322271)
      JCL - 20161018_01 based on Oracle jdk8u111-b14

      Testsuite: https://github.com/jboss-eap-qe/vdx-wildfly-testsuite
      Jenkins job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-PrettyPrint/job/eap-7x-pretty-print-smoke-rhel-ibm/

      Failing tests:

      • JBossWSTestCase#incorrectValueOfModifyWsdlAddressElement
      • JBossWSTestCase#modifyWsdlAddressElementWithNoValue
      • 4x JBossWSDomainTestCase#modifyWsdlAddressElementWithNoValue*

      Run one test for standalone: mvn -Djboss.home=/home/rsvoboda/TESTING/710DR10/jboss-eap-7.1 test -Dtest=$TEST
      Run one test for domain: use ^^^ add -Ddomain

      Attached details from tests runs using Oracle and IBM JDK, executed JBossWSTestCase#incorrectValueOfModifyWsdlAddressElement and JBossWSTestCase#modifyWsdlAddressElementWithNoValue tests. -nodocs variants are when I removed docs directory (=> no VDX ) to see raw error messages.

      Preliminary conclusion:
      It seems that for Oracle JDK and OpenJDK VDX removes WFLYCTL0097: from the caused by error message, but for IBM JDK it is present in the message - e.g. ' ^^^^ "WFLYCTL0097: Wrong type for 'modify-wsdl-address'. ...'.
      For IBM JDK the The primary underlying error message was: part is different than for Oracle case.

      Lets use case for incorrectValueOfModifyWsdlAddressElement:
      Oracle:

      |  387:     <modify-wsdl-address>ttrue</modify-wsdl-address>
      |                                ^^^^ Wrong type for 'modify-wsdl-address'. Expected [BOOLEAN] but was
      |                                       STRING
      |
      |  388:   </subsystem>
      |  389:   <subsystem xmlns="urn:jboss:domain:weld:3.0"/>
      |  390: </profile>
      |
      | The primary underlying error message was:
      | > ParseError at [row,col]:[387,28]
      | > Message: "WFLYCTL0097: Wrong type for 'modify-wsdl-address'. Expected
      | >   [BOOLEAN] but was STRING"
      

      IBM:

      |  387:     <modify-wsdl-address>ttrue</modify-wsdl-address>
      |                                ^^^^ "WFLYCTL0097: Wrong type for 'modify-wsdl-address'. Expected [BOOLEAN]
      |                                       but was STRING"
      |
      |  388:   </subsystem>
      |  389:   <subsystem xmlns="urn:jboss:domain:weld:3.0"/>
      |  390: </profile>
      |
      | The primary underlying error message was:
      | > "WFLYCTL0097: Wrong type for 'modify-wsdl-address'. Expected [BOOLEAN]
      | > but was STRING"
      

      When I disabled pretty print I got this:
      Oracle:

      08:56:10,894 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
      	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143) [wildfly-controller-3.0.0.Alpha17-redhat-1.jar:3.0.0.Alpha17-redhat-1]
      	at org.jboss.as.server.ServerService.boot(ServerService.java:373) [wildfly-server-3.0.0.Alpha17-redhat-1.jar:3.0.0.Alpha17-redhat-1]
      	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:314) [wildfly-controller-3.0.0.Alpha17-redhat-1.jar:3.0.0.Alpha17-redhat-1]
      	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]
      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[387,28]
      Message: "WFLYCTL0097: Wrong type for 'modify-wsdl-address'. Expected [BOOLEAN] but was STRING"
      

      IBM:

      08:55:01,335 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
      	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143) [wildfly-controller-3.0.0.Alpha17-redhat-1.jar:3.0.0.Alpha17-redhat-1]
      	at org.jboss.as.server.ServerService.boot(ServerService.java:373) [wildfly-server-3.0.0.Alpha17-redhat-1.jar:3.0.0.Alpha17-redhat-1]
      	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:314) [wildfly-controller-3.0.0.Alpha17-redhat-1.jar:3.0.0.Alpha17-redhat-1]
      	at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0]
      Caused by: javax.xml.stream.XMLStreamException: "WFLYCTL0097: Wrong type for 'modify-wsdl-address'. Expected [BOOLEAN] but was STRING"
      

      cc tcrawley

      Attachments

        Issue Links

          Activity

            People

              tcrawley Toby Crawley (Inactive)
              rsvoboda@redhat.com Rostislav Svoboda
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: