How to Make a Managed Server to Be Marked as Unhealthy on a Datasource Deployment/Initialization Failure on Startup (Doc ID 2772952.1)

Last updated on AUGUST 12, 2024

Applies to:

Oracle WebLogic Server - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Goal

How to make A Managed Server to be marked as unhealthy when a Datasource Deployment/Initialization Failure On Startup.

If a failure occurs while populating the initial capacity connections in the connection pool, the data source is not deployed (it won't be in JNDI so the application will fail to find it) but the server continues to startup and is not marked as unhealthy. In some applications, a data source may be a critical resource such that no useful processing can be done if the data source is not deployed and in such cases the user may want the server not to reach running state.

Solution

	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

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How to Make a Managed Server to Be Marked as Unhealthy on a Datasource Deployment/Initialization Failure on Startup (Doc ID 2772952.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!