Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2948

[EAP][CD] eap-cd-tx-recovery-s2i still no "updated via JMS" message for the second entry after recovery

    XMLWordPrintable

Details

    Description

      Following the quickstart scenario for the https://github.com/jboss-container-images/jboss-eap-7-openshift-image/blob/eap-cd-dev/templates/eap-cd-tx-recovery-s2i.json template

      the instructions at

      https://github.com/jboss-openshift/openshift-quickstarts/tree/master/jta-crash-rec-eap

      After the recovery occurs and the EAP pod is scaled back to one, the second entry does not show the "updated via JMS" entry, which suggests the recovery did not occur as expected and the state is inconsistent.

      Attachments

        1. CLOUD-2948.tar
          120 kB
        2. after.log
          29 kB
        3. before.log
          37 kB
        4. broker.log
          8 kB
        5. recovery.log
          41 kB

        Issue Links

          is blocked by

          Task - Represents a small unit of work that is not end-user facing. JBEAP-15714 Update the Using the JTA Crash Recovery Application section of the OCP guide.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              kwills@redhat.com Ken Wills
              maschmid@redhat.com Marek Schmidt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: