-
Bug
-
Resolution: Done
-
Major
-
7.3.0.GA
-
None
-
OpenShift
Kie Server template with MySQL
-
CR1
-
-
-
-
-
-
CR1
-
https://github.com/jboss-container-images/rhpam-7-openshift-image/pull/251, https://github.com/jboss-container-images/rhpam-7-openshift-image/pull/252, https://github.com/jboss-container-images/rhpam-7-openshift-image/pull/256, https://github.com/jboss-container-images/rhpam-7-openshift-image/pull/257, https://github.com/kiegroup/kie-cloud-operator/pull/107, https://github.com/ansibleplaybookbundle/rhpam-apb/pull/53, https://github.com/ansibleplaybookbundle/rhpam-apb/pull/54
-
2019 Week 11-13, 2019 Week 14-16
There is a race condition in setting of deployment when is EJB initialized first, before DB is started.
In this case was first set up EJB, then was DB started and then Kie Server was started. In this case ready and health check passed and everything looks OK and running. In Kie Server log are EJB exceptions (see log in attachments). To find out that configuration is not OK user must look to Kie Server log.
To fix EJB configuration Kie Server needs to be respin. I delete pod with the EJB exception and after that a new Kie Server was created. In the new pod there is no EJB exception in log and Kie Server is started.
- relates to
-
RHPAM-1165 Wrong start order of Kie server and database in templates
- Closed