The Monitor1.0 catalog contains messages in the range
BEA2012400 - BEA2012499.
|
BEA-2012400
|
Info: The LOC bundle name has successfully started.
|
Description
| The LOC bundle name has successfully been started by the OSGi framework of the LOC process. |
|
Cause
| Normal operation. |
|
Action
| No Action Required. |
|
|
BEA-2012401
|
Error: An unexpected exception was encountered in the Monitor. Exception: x Context: context. Result: action.
|
Description
| An unexpected exception was encountered in the Monitor: x. Activity in process at the time of the exception was: context. As a result of this exception the following action is being taken: action. |
|
Cause
| Internal problem. |
|
Action
| The Monitor will attempt to recover but quality of service might be compromised. It is advised that the problem be diagnosed which might require involving BEA support. |
|
|
BEA-2012402
|
Error: An unexpected problem occurred during processing in the Monitor. Problem: issue. Context: context. Result: action.
|
Description
| An unexpected problem occurred in the Monitor: issue. Activity in process at the time of the exception was: context. As a result of this exception the following action is being taken: action. |
|
Cause
| Internal problem. |
|
Action
| The Monitor will attempt to recover but quality of service might be compromised. It is advised that the problem be diagnosed which might require involving BEA support. |
|
|
BEA-2012403
|
Warning: A null deleted item was returned for deleted items in an observed value. observer Id : observerId and attribute name : attributeName.
|
Description
| A null deleted item was returned for deleted items in an observed value. observer Id : observerId and attribute name : attributeName. |
|
Cause
| Internal problem. |
|
Action
| Notify system administrator. |
|
|
BEA-2012404
|
Info: Unable to find the service name and process type for process processId.
|
Description
| Unable to find the service name and process type for process processId. |
|
Cause
| This can happen when processes are killed beofre they fully come up. |
|
Action
| This can happen when processes are killed beofre they fully come up. |
|
|
BEA-2012405
|
Error: There was an error executing an internal monitor action : msg
|
Description
| There was an error executing an internal monitor action : msg |
|
Cause
| This is due to an internal error. |
|
Action
| BEA support should be consulted. |
|
|
BEA-2012406
|
Error: There was an error scheduling an internal monitor action : msg : t.
|
Description
| There was an error scheduling an internal monitor action : msg : t. |
|
Cause
| This is due to an internal error. |
|
Action
| BEA support should be consulted. |
|
|
BEA-2012407
|
Error: There was an an unexpected exception processing new observed values : t.
|
Description
| There was an an unexpected exception processing new observed values : t. |
|
Cause
| This is due to an internal error. |
|
Action
| BEA support should be consulted. |
|
|
BEA-2012408
|
Error: There was an an error observing a metric : error. If this error persists contact administrator. Is Removed : isRemoved
|
Description
| There was an an error observing a metric : error. If this error persists contact administrator. Is Removed : isRemoved |
|
Cause
| This is due to an observation error. |
|
Action
| BEA support should be consulted. |
|
|
BEA-2012499
|
Info: The LOC bundle name has successfully been stopped.
|
Description
| The LOC bundle name has successfully been stopped by the OSGi framework of the LOC process. |
|
Cause
| Normal operation. |
|
Action
| No action required. |
|
