Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-19156

EE 8->9 Deployment transform error with a ds.xml file

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • None
    • Server
    • None
    • ---
    • ---

    Description

      As part of the work on WFLY-19150 I attempted to remove this line from the testsuite/integration/pom.xml surefire configuration systemPropertyVariables section:

      <server.jvm.args>${server.jvm.args} -Dorg.wildfly.unsupported.skip.jakarta.transformer=true</server.jvm.args>
      

      But this leads to failures in DeployedXmlDataSourceManagementTestCase when testing WildFly Preview.

      The server log shows this happening when the test's ServerSetupTask executes:

      2024-03-20 01:06:27,564 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /opt/buildAgent/work/e34a6f994de9f7c6/testsuite/integration/basic/target/wildfly/standalone/data/content/b0/4f3ee8f5e43fa3b162981b50bb72fe1acabb33/content
      2024-03-20 01:06:27,567 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "test2-ds" (runtime-name: "test2-ds.xml")
      2024-03-20 01:06:27,586 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."test2-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."test2-ds.xml".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "test2-ds.xml"
      	at org.jboss.as.server@24.0.0.Beta2//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:179)
      	at org.jboss.msc@1.5.3.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1617)
      	at org.jboss.msc@1.5.3.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1580)
      	at org.jboss.msc@1.5.3.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1438)
      	at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
      	at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
      	at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
      	at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
      	at java.base/java.lang.Thread.run(Thread.java:840)
      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: ParseError at [row,col]:[1,1]
      Message: Content is not allowed in prolog.
      	at org.jboss.as.connector@32.0.0.Beta1-SNAPSHOT//org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:86)
      	at org.jboss.as.server@24.0.0.Beta2//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
      	... 8 more
      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
      Message: Content is not allowed in prolog.
      	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:652)
      	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1346)
      	at org.jboss.ironjacamar.impl@3.0.8.Final//org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:107)
      	at org.jboss.ironjacamar.impl@3.0.8.Final//org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:79)
      	at org.jboss.as.connector@32.0.0.Beta1-SNAPSHOT//org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:71)
      	... 9 more
      
      2024-03-20 01:06:27,588 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "test2-ds")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test2-ds.xml\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"test2-ds.xml\"
          Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: ParseError at [row,col]:[1,1]
      Message: Content is not allowed in prolog.
          Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
      

      Apparently turning off the disabling of deployment transformation results in some flaw in the transformation of the testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/deployment/xml/datasource/test2-ds.xml file.

      The file content seems reasonable and is pretty similar to other ds.xml files deployed in the same test.:

      <?xml version="1.0" encoding="UTF-8"?>
      <!--
        ~ Copyright The WildFly Authors
        ~ SPDX-License-Identifier: Apache-2.0
        -->
      
      <datasources xmlns="http://www.jboss.org/ironjacamar/schema">
          <datasource jndi-name="java:jboss/datasources/Deployed2DS" enabled="true" use-java-context="true"
                      pool-name="H2DS">
              <connection-url>jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
              <driver>h2</driver>
              <pool></pool>
              <security>
                  <user-name>sa</user-name>
                  <password>sa</password>
              </security>
          </datasource>
      </datasources>
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: