Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Description
If standalone-openshift.xml is brought from jboss-eap-7/eap71-openshift or jboss-eap-7/eap72-openshift to jboss-eap-7/eap73-openjdk8-openshift-rhel7, and even if the environment variable ENABLE_GENERATE_DEFAULT_DATASOURCE=true is set, then the following error occurs when starting the EAP7.3 container:
WARN You have set environment variables to configure the datasource in the default-bindings in the ee subsystem subsystem which conflicts with the value that already exists in the base configuration. The base configuration value will be used. Fix your configuration. ... 04:08:33,987 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "echo.war")]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.echo.echo.env.##DEFAULT_DATASOURCE##"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.echo.echo.DefaultDataSource is missing [jboss.naming.context.java.module.echo.echo.env.##DEFAULT_DATASOURCE##]"] }
In this error occurs, the place holder ##DEFAULT_DATASOURCE## is not replaced during starting up container.
<default-bindings context-service="java:jboss/ee/concurrency/context/default" datasource="##DEFAULT_DATASOURCE##" <<<=== jms-connection-factory="java:jboss/DefaultJMSConnectionFactory" managed-executor-service="java:jboss/ee/concurrency/executor/default" managed-scheduled-executor-service="java:jboss/ee/concurrency/scheduler/default" managed-thread-factory="java:jboss/ee/concurrency/factory/default"/>
Attachments
Issue Links
- clones
-
JBEAP-19167 [GSS](7.3.z) Placeholder ##DEFAULT_DATASOURCE## is not replaced during the container startup process
- Verified
- is cloned by
-
CLOUD-3549 [GSS](CD20) Placeholder ##DEFAULT_DATASOURCE## is not replaced during the container startup process
- New