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

[EAP][XA] jta-crash-rec-eap quickstarts needs to use proper messaging and database datasource

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Won't Do
    • Major
    • None
    • None
    • EAP6, EAP7
    • None

    Description

      The quickstart jta-crash-rec-eap* does not use proper datasource and messaging which would show the proper setup of EAP app server in OpenShift environment.

      The jta quickstart uses H2 database which saves data locally at data directory of the migration pod. The same there is JMS messaging set up to use in-VM ActiveMQ broker. This is not how the application should be set up for the cloud/OpenShift environment. The datasources needs to be separate services that is independent to the application (server). The quickstart in current shape shows misguiding recipe to cloud development while it does not work properly in showing the crash recovery capabilities.

      (see comments at https://issues.jboss.org/browse/CLOUD-2760)

      Attachments

        Issue Links

          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-2768 [EAP][XA] merge jta-crash-rec-eap quickstarts and update README

          • 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.
          • New
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17015 Sometimes happens that jta-crash-rec quickstart fails after scaling up EAP deployment

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-2938 [EAP][XA] jta-crash-rec-eap quickstarts should use correct settings with remote AMQ7 broker

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-2760 [EAP][XA] jta-crash-rec-eap7 quickstart doesn't work with sprint-21 img

          • Critical - To be worked on immediately following BLOCKER issues.
          • New

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21986 Remove eap74-tx-recovery-s2i.json

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: