Uploaded image for project: 'WildFly WIP'
  1. WildFly WIP
  2. WFWIP-201

incomplete tx recovery on openshift

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • OpenShift

    Description

      While testing tx recovery in OpenShift I see that recovery doesn't completely finish in some tests.

      Scenario:

      ejb client (app tx-client, pod tx-client-0):

      • EJB business method
        • lookup remote EJB
        • enlist XA resource 1 to transaction
        • enlist XA resource 2 to transaction
        • call remote EJB

      ejb server (app tx-server, pod tx-server-0):

      • EJB business method
        • enlist XA resource 1 to transaction
        • enlist XA resource 2 to transaction

      ejb server XA resource 2 crashes JVM in commit method phase. (the same outcome client crashes at commit phase)

      Test waits until crashed pod is restarted, then forces periodic recovery twice and then checks that transaction log store is empty. But it is not empty, however it looks like all XA resources were commited.

      Attached are logs from client and server pods.

      Attachments

        1. auth_fail.txt
          545 kB
        2. tx-client-0.txt
          2.09 MB
        3. tx-server-0.txt
          2.62 MB

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4659 Partial revert of *not* having static default authentication context

          • 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
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFTC-75 XA file registry does not delete records when network failure happens during commit

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

          Bug - A problem that impairs or prevents the functions of the product. WFWIP-203 Transaction recovery may hit a wrong server when remote side works with multiple pods

          • 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.
          • Resolved

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-12453 Update wildfly-transaction-client to 1.1.7.Final

          • 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

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

              Dates

                Created:
                Updated:
                Resolved: