How to Mitigate the Impact of Complete Server/Cluster Outages Due to OutOfMemoryErrors (OOME) or High CPU Conditions in WebLogic Server (WLS)
Last updated on DECEMBER 14, 2016
Applies to:Oracle WebLogic Server - Version 9.2 to 10.0
Information in this document applies to any platform.
The goal of this article is to avoid production server or cluster outages due to unknown/unexpected conditions, and to mitigate their impact when they do occur, as described below.
This article states below -
"Overload protection can be configured in two ways. The administrator can configure a panic action due to OOME/Free-Memory-Percent-Low-Threshold, and a failure action due to the stuck threads count. These are configured using the Administration Console."
This does not hold true to current 10.3 and 12c releases.
Per WLS 10.3.x documentation - we have Panic action only triggered with unhandled OOME.
Oracle documentation Servers: Configuration: Overload < http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/pagehelp/Corecoreserverserverconfigoverloadtitle.html >
There are now 2 arguments available to use:
Free Memory Percent Low Threshold
Percentage free memory below which the server is considered overloaded. WorkManagers perform overloadAction once the server is marked as overloaded.
Free Memory Percent High Threshold
Percentage free memory after which the server overload condition is cleared. WorkManagers stop performing overloadActions and start regular execution once the overload condition is cleared.
The remainder of this article kept in tact for historical purposes...
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms