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

[Quickstart] jta-crash-rec-eap emit `Unable to acquire JDBC Connection` error

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • None
    • EAP7
    • None

    Description

      Following instructions from https://github.com/jboss-openshift/openshift-quickstarts/tree/master/jta-crash-rec-eap We see intermittently `Unable to acquire JDBC Connection`

      We see it in test, but was also able to simulate manually by running multiple requests in paralel.

      Attachments

        1. eap.log
          72 kB
          Martin Choma

        Issue Links

          relates to

          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

          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

          Activity

            People

              Unassigned Unassigned
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: