Long-running transaction processing may fail in Red Hat build of Keycloak due to the transaction timeout

Solution Verified - Updated -

Issue

In Red Hat build of Keycloak (RHBK), processing that runs for a long time within a single transaction may stop before completion.

This issue can occur when the processing time exceeds the transaction timeout.

Examples include the following:

  • User synchronization from a federated user store
  • Importing a realm that contains a large number of users
  • Other processing that keeps a single transaction open for a long time

In such cases, the transaction timeout may be reached before the processing completes, resulting in the failure of the operation.

Environment

  • Red Hat Build of Keycloak (RHBK)
     - 22.0
    • 24.0
    • 26.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content