You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current arrangement the RedisConnectionFactory implementations are implementing both, InitializingBean and SmartLifecycle (See also #2502). Though, for historic reasons they eagerly try to connect to the Redis server already in afterPropertiesSet() which is not in line with the actual intent of the method aiming to verify properties leaving the startup to Lifecycle#start().
For Checkpoint restore and CDS training runs we'd need to move this arrangement into its desired state without breaking existing applications potentially relying on the eager initialization of the connection factory.
The text was updated successfully, but these errors were encountered:
mp911de
changed the title
Allow RedisConnectionFactories to be intialized as part of the context lifecycle.
Allow RedisConnectionFactories to be intialized as part of the context lifecycle
Mar 13, 2024
mp911de
changed the title
Allow RedisConnectionFactories to be intialized as part of the context lifecycle
Allow RedisConnectionFactories to be initialized as part of the context lifecycle
Mar 13, 2024
…xt lifecycle.
Lettuce and Jedis connection factories now can be configure to initialize early during afterPropertiesSet or configured whether the component should be auto-started by the container.
By default, connection factories auto-startup early.
Closes#2866
…xt lifecycle.
Lettuce and Jedis connection factories now can be configured to initialize early during afterPropertiesSet or configured whether the component should be auto-started by the container.
By default, connection factories auto-startup early.
Closes#2866
In the current arrangement the
RedisConnectionFactory
implementations are implementing both,InitializingBean
andSmartLifecycle
(See also #2502). Though, for historic reasons they eagerly try to connect to the Redis server already inafterPropertiesSet()
which is not in line with the actual intent of the method aiming to verify properties leaving the startup toLifecycle#start()
.For Checkpoint restore and CDS training runs we'd need to move this arrangement into its desired state without breaking existing applications potentially relying on the eager initialization of the connection factory.
The text was updated successfully, but these errors were encountered: