Managed Server Goes Into Running State Even When Failing To Initialize DB Connection
(Doc ID 2539850.1)
Last updated on OCTOBER 01, 2020
Applies to:Oracle WebLogic Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
When starting a managed server in WebLogic Server 10.3.6, if a data source fails to connect to the Database for whatever reason the managed server fails to initialized and goes to "ADMIN" state. That triggers some alerts that help us resolve the issue in a timely manager.
However, after upgrading that Weblogic domain from 10.3.6 to 18.104.22.168, if the data source fails to connect to the database, the managed server still goes to "RUNNING" state but, the applications will fails to get activated.
How can we have the same functionality from 10.3.6 in 22.214.171.124?
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