-
Bug
-
Resolution: Won't Do
-
Critical
-
None
-
None
Suppose a deployment built on eap72-openjdk11-openshift-rhel8 image with the following environment variables that assured that the server would point timer service towards java:jboss/datasources/postgres datasource previously (with eap72-openshift images):
...
- env: - name: DB_SERVICE_PREFIX_MAPPING
value: testdb-postgresql=TESTDB_POSTGRESQL
- name: TESTDB_POSTGRESQL_PASSWORD
value: testpwd
- name: TIMER_SERVICE_DATA_STORE
value: testdb-postgresql
- name: TESTDB_POSTGRESQL_DATABASE
value: testdb
- name: TESTDB_POSTGRESQL_JNDI
value: 'java:jboss/datasources/postgres'
- name: TESTDB_POSTGRESQL_USERNAME
value: testuser
...
EAP does not have any /subsystem=ejb3/service=timer-service configured. This is a change compared to eap72-openshift image, where the timer service gets properly configured.
eap72-openjdk11-openshift-rhel8
[standalone@localhost:9990 /] /subsystem=ejb3/service=timer-service:read-resource
/subsystem=ejb3/service=timer-service:read-resource
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0216: Management resource '[
(\"subsystem\" => \"ejb3\"),
(\"service\" => \"timer-service\")
]' not found",
"rolled-back" => true
}
eap72-openshift
[standalone@localhost:9990 /] /subsystem=ejb3/service=timer-service:read-resource
{
"outcome" => "success",
"result" => {
"default-data-store" => "testdb_postgresql-TESTDB_POSTGRESQL_ds",
"thread-pool-name" => "default",
"database-data-store" => {"testdb_postgresql-TESTDB_POSTGRESQL_ds" => undefined},
"file-data-store" => {"default-file-store" => undefined}
}
}
- clones
-
-
- Closed
-
