The ObserverAgent1.0 catalog contains messages in the range
BEA2016200 - BEA2016299.
|
BEA-2016200
|
Info: The bundle name has successfully started.
|
Description
| The bundle name has successfully been started by the OSGi framework. |
|
Cause
| Normal operation. |
|
Action
| No Action Required. |
|
|
BEA-2016201
|
Error: An unexpected error ocurred whilst removing the Observer ObsName, due to its associated process terminating. Ignoring the error: excp
|
Description
| It is normal for Observers to shutdown as a result of the associated process shutting down. At this point any errors in the Observer cause no harm so can be safely ignored. |
|
Cause
| Unknown error. |
|
Action
| The current application is unaffected. But please notify BEA support that this occurred. |
|
|
BEA-2016202
|
Warning: JVM with ID: jvmID terminated before all connections could be established. Last connect exception encountered was: excp.
|
Description
| A managed process may exit for any number of reasons. In this case the process with ID: jvmID existed in an early stage - before the MBeanServer connection could be established. |
|
Cause
| This process may have exited for legitimate reasons such as a manual termination by the user. In some cases the process may be terminated because a JMX connection could not be established in a reasonable period of time. If that occurs, the controller log will contain corresponding messages. An inability to establish a JMX connection indicates a communication problem that needs to be addressed. |
|
Action
| The user should determine why the process exited and take the appropriate action. If the process was taken down by WLOC due to an inability to establish a timely JMX connection, then the user needs to determine why the connection process is failing. This may require support from BEA. |
|
|
BEA-2016203
|
Warning: JVM with ID: jvmID terminated after teh JVM connection was established but before the corresponding Observer was registered with the Controller.
|
Description
| A managed process may exit for any number of reasons. In this case the process with ID: jvmID existed in an early stage - before the Controller registration occurred. However the MBeanServer connection had been established by the agent process. |
|
Cause
| This process may have exited for legitimate reasons such as a manual termination by the user. In some cases the process may be terminated because a JMX connection could not be established in a reasonable period of time. If that happened here then the connection was eventually established, but the controller timed out before the corresponding Observer was registered. This can be verified in the controller log which will contain corresponding messages indicating the timeout. |
|
Action
| If the exit was dues to a controller timeout the user may want to determine why the MBeanServer connection took so long. |
|
|
BEA-2016204
|
Error: An unexpected exception was encountered in the AgentLumperObserver. Exception: [x] Context: context. Result: action.
|
Description
| An unexpected exception was encountered in the AgentLumperObserver: [x]. Activity in process at the time of the exception was: context. As a result of this exception the following action(s) is(are) being taken: action. |
|
Cause
| Internal problem. |
|
Action
| The Observer 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-2016205
|
Error: An unexpected problem occurred during processing in the AgentLumperObserver. Problem: "issue". Context: context. Result: action.
|
Description
| An unexpected problem occurred in the AgentLumperObserver: "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 Observer 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-2016299
|
Info: The bundle name has successfully been stopped.
|
Description
| The bundle name has successfully been stopped by the OSGi framework. |
|
Cause
| Normal operation. |
|
Action
| No action required. |
|
