The Health1.0 catalog contains messages in the range
BEA310000 - BEA319999. Messages in this catalog are part of the
weblogic.health
Internationalization package and the weblogic.health Localization package.
|
BEA-310000
|
Debug: arg0
|
Description
| Uncatalogued debug message - please do not change. |
|
Cause
| Debugging - please do not change. |
|
Action
| No action required. |
|
|
BEA-310001
|
Error: Subsystem name has failed. Setting server state to Failed.
|
Description
| One of the critical subsystems of the server has failed. |
|
Cause
| One of the critical subsystems of the server has failed. |
|
Action
| Check the server log to determine the cause of the subsystem failure. |
|
|
BEA-310002
|
Info: newValue% of the total memory in the server is free
|
Description
| Free memory in the server has changed |
|
Cause
| Free memory in the server has changed |
|
Action
| no action required. |
|
|
BEA-310003
|
Critical: Free memory in the server is freeMemory bytes. There is danger of OutOfMemoryError
|
Description
| Free memory in the server is very low |
|
Cause
| Free memory in the server is very low |
|
Action
| TBD. add description of overload actions |
|
|
BEA-310004(retired)
|
Info: Memory monitoring has started. The maximum memory configured is maxMemoryK
|
Description
| Memory monitoring has started |
|
Cause
| Memory monitoring has started |
|
Action
| TBD. add description on how to turn it off |
|
|
BEA-310005(retired)
|
Error: Memory monitoring has stopped. e
|
Description
| Memory monitoring has stopped |
|
Cause
| Memory monitoring has stopped |
|
Action
| Internal server error. Contact support with server log |
|
|
BEA-310006
|
Critical: Critical Subsystem name has failed. Setting server state to FAILED.\nReason: reason
|
Description
| One of the critical subsystems of the server has failed. |
|
Cause
| One of the critical subsystems of the server has failed. |
|
Action
| Check the server log to determine the cause of the subsystem failure. |
|
|
BEA-310007
|
Warning: Subsystem name has failed because of: reason Notifaction did not happen, however, because name was not registered with the HealthMonitorService.
|
Description
| Subsystem name has failed because of: reason Notifaction did not happen, however, because name was not registered with the HealthMonitorService. |
|
Cause
| One of the subsystems of the server has failed. |
|
Action
| Check the server log to determine the cause of the subsystem failure. MigratableTargets may need to be manually moved, since the automatic migration subsystem requires HealthMonitor notification to work properly. |
|
|
BEA-310008
|
Critical: Non critical Subsystem name has failed.\nReason: reason
|
Description
| One of the non-critical subsystems of the server has failed. The server will continue running |
|
Cause
| One of the non-critical subsystems of the server has failed. |
|
Action
| Check the server log to determine the cause of the subsystem failure. |
|
