Closed
Description
Before reporting an issue
- I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
Area
core
Describe the bug
Upgrading from Keycloak 24 to 26.0.10 (Red Hat build), I notice that it no longer starts successfully with optimized startup, due to passing the expect-continue-enabled
option.
Version
26.0.10
Regression
- The issue is a regression
Expected behavior
Keycloak starts up successfully, and the DefaultHttpClientFactory
determines the desired value for expect-continue-enabled
at runtime.
Actual behavior
Keycloak starts up with an error:
The following build time options have values that differ from what is persisted - the new values will NOT be used until another build is run: kc.spi-connections-http-client-default-expect-continue-enabled
How to Reproduce?
- Create an optimized Keycloak image
- start the server in production mode, passing both
--optimized
and--spi-connections-http-client-default-expect-continue-enabled=true
Anything else?
I'm not familiar with how Keycloak determines build-time options to persist, but it seems strange to me that this is the only connections SPI option that is flagged, since there are others like socket-timeout-millis
that I pass. I did notice that the option is absent in the factory's getConfigMetadata()
method: