Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Deferred
    • Affects Version/s: 4.1.0.Final
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      According to the experts from transaction team, it is good to ensure that JTA transaction are short running. Having long-running transactions is not a good practice.

      We currently require some long-running transactions for some scenarios (EG. At this moment it is preloading offline sessions at startup. See KEYCLOAK-7745 ) and we use longer timeouts for them ( KeycloakModelUtils.runJobInTransactionWithTimeout ). Will be good to check if it's possible to skip JTA transaction at all for such long-running transactions, which are doing just "coordination".

      There is an option to start KeycloakSession without transaction, but I am not sure about all the possible side-effects for this (EG. what happens if there are some DB calls within that coordinating transaction and datasource is configured to be XA).

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  mposolda Marek Posolda
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: