Persistence enabled Federation Cluster Servers failing with startup timeout errors on Server Restarts in FMW domains
(Doc ID 2783248.1)
Last updated on JUNE 13, 2022
Applies to:Oracle Coherence - Version 220.127.116.11.0 and later
Oracle WebLogic Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Customer has reported that running into issues with data-persistence testing where the cache works fine without persistence enabled, but then as soon as enable data persistence it becomes unstable and rarely even starts up properly. What could be the issue here? Have tried enabling data persistence through the WebLogic Admin console, through server startup arguments, and through the actual cache config themselves. All of them have had the same behavior. Rarely the cache has even worked correctly and persisted data, but that has only happened a couple of times through many, many restarts using the same builds/settings/etc.
When the servers restarted in the domain, the application deployments failed as follows:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document