Coherence Arguments Do Not Take Effect When They Are Set As Startup Settings Of A WebLogic Server In The Administration Console And The Server Is Started From The Command Line Directly (Doc ID 1304590.1)

Last updated on FEBRUARY 16, 2024

Applies to:

Oracle Coherence - Version 3.5.0 and later
Information in this document applies to any platform. *** ***

Symptoms

When a Coherence argument, such as -Dtangosol.coherence.cluster, is set as startup setting of a server in the WebLogic Server Administration Console, and then the server is started up from a console by running a shell script, the specified Coherence settings do not take effect.

Cause

	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

Symptoms

Cause

Solution

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

Coherence Arguments Do Not Take Effect When They Are Set As Startup Settings Of A WebLogic Server In The Administration Console And The Server Is Started From The Command Line Directly (Doc ID 1304590.1)

Applies to:

Symptoms

Cause

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

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