Repository navigation
Replies: 2 comments 1 reply
There are several potentially long running operations in Keycloak - namely import and export - the 5 minute timeout is typically good enough for those operations. There are several issues to refine timeout behavior further - #36710 |
|
If a SPI experiences a prolonged blocking operation that exceeds the quarkus.transaction-manager.default-transaction-timeout=300 threshold, will this transaction timeout forcibly terminate the background task running in the worker thread? Additionally, we would like to understand whether Keycloak has any recovery mechanisms for handling long-running background tasks in worker threads. @shawkins Any idea on the above query? |
If the operation is wrapped in a transaction, yes.
By this do you mean retries? Can include more details on how the SPI is starting the background task? |
Uh oh!
There was an error while loading. Please reload this page.
Hey Team,
We noticed that the value for
"quarkus.transaction-manager.default-transaction-timeout"is set to 300 seconds in the filequarkus/runtime/src/main/resources/application.properties, whereas the default Quarkus value for this property is 60 seconds.Reference: Quarkus Configuration Guide.
Could you provide insight into why this value was modified from 60s to 300s in Keycloak?
Thanks!
All reactions