[jboss-jira] [JBoss JIRA] (WFCORE-2172) VDX - pretty print gives different message on IBM JDK than on Oracle/OpenJDK for incorrect value of element or unexpected empty element
Brian Stansberry (JIRA)
issues at jboss.org
Tue Jan 10 10:54:00 EST 2017
[ https://issues.jboss.org/browse/WFCORE-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry moved JBEAP-8192 to WFCORE-2172:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2172 (was: JBEAP-8192)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
Affects Version/s: (was: 7.1.0.DR10)
> VDX - pretty print gives different message on IBM JDK than on Oracle/OpenJDK for incorrect value of element or unexpected empty element
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2172
> URL: https://issues.jboss.org/browse/WFCORE-2172
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Rostislav Svoboda
> Assignee: Toby Crawley
>
> 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:
> {code}
> | 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"
> {code}
> IBM:
> {code}
> | 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"
> {code}
> When I disabled pretty print I got this:
> Oracle:
> {code}
> 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"
> {code}
> IBM:
> {code}
> 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"
> {code}
> cc [~tcrawley]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list