-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
EAP70 1.6.0.GA, EAP71 1.0.0.GA
-
None
The standalone-openshift.xml file contains invalid xml before being processed by scripts at deploy time. This can cause issues for customers wanting to use this file as a default configuration starting point.
The issue seems to be around this block https://github.com/jboss-openshift/cct_module/blob/1.0/os-eap70-openshift/added/standalone-openshift.xml#L169-L174.
<default-bindings context-service="java:jboss/ee/concurrency/context/default" <!-- ##DEFAULT_DATASOURCE## --> ##DEFAULT_JMS## 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"/>
- duplicates
-
CLOUD-1945 Initial state of standalone-openshift.xml should be valid XML
-
- Verified
-