-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
CLOUD Maintenance Sprint 22
jta-crash-rec-eap7 doesn't work correctly with jboss-eap-7/eap71-openshift:1.4-5 image.
Steps to work with QS are described in doc .
Doing scale down after starting second transaction leads to recovery in migration pod (which looks ok) but bringing back the app with scale up leads to empty table (looks like even the first record didn't survive the scale down) .
It works OK for me with previous jboss-eap-7/eap71-openshift:1.3. Maybe I am missing something....
- is related to
-
CLOUD-2761 [EAP][Recovery] Migration pod starts with permission errors in log
- Closed
-
CLOUD-2795 [EAP][XA] jta-crash-rec-eap quickstarts needs to use proper messaging and database datasource
- Closed
- relates to
-
CLOUD-2766 [EAP][Templates] eap71-tx-recovery-s2i template params don't make sense
- Verified
-
CLOUD-2261 [EAP][XA][Recovery][NFS] split lock is broken after a minute of network partition
- Closed
-
CLOUD-2768 [EAP][XA] merge jta-crash-rec-eap quickstarts and update README
- New