Cannot boot Red Hat Single Sign-On because "Lock didn't yet acquired"

Solution Unverified - Updated -


In our system which using a 2 Red Hat Single Sign-On (RH-SSO) instances configuration, an error occurred while the RH-SSO was booting. The error message is shown below.

17:45:27,088 WARN [org.keycloak.connections.jpa.updater.liquibase.lock.CustomLockService] (ServerService Thread Pool -- 62) Lock didn't yet acquired. Will possibly retry to acquire lock. Details: ERROR: cannot execute SELECT FOR UPDATE in a read-only transaction [Failed SQL: SELECT ID FROM public.databasechangeloglock WHERE ID=1000 FOR UPDATE]


  • Red Hat Single Sign-On(RH-SSO)
    • 7.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