Skip to content

Commit 2e8aecf

Browse files
committed
minor fixes to config overrides doc
1 parent 68bcd41 commit 2e8aecf

File tree

1 file changed

+1
-1
lines changed
  • docs-source/content/userguide/managing-domains/configoverrides

1 file changed

+1
-1
lines changed

docs-source/content/userguide/managing-domains/configoverrides/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -338,7 +338,7 @@ spec:
338338
339339
Incorrectly formatted override files may be accepted without warnings or errors and will not prevent WebLogic pods from booting. So, it is important to make sure that the template files are correct in a QA environment, otherwise your WebLogic Servers may start even though critically required overrides are failing to take effect.
340340
341-
On WebLogic servers that support the weblogic.SituationalConfig.failBootOnError system property ( Note: it is not supported in WebLogic 12.2.1.3 ),
341+
On WebLogic Servers that support the `weblogic.SituationalConfig.failBootOnError` system property ( Note: It is not supported in WebLogic Server 12.2.1.3 ),
342342
by default the WebLogic server will fail to boot if any situational configuration files are invalid.
343343
This can be configured by using the `failBootOnSituationalError` attribute in the Domain spec to `false` to start up the WebLogic servers even with
344344
incorrectly formatted override files.

0 commit comments

Comments
 (0)