The PushManager1.0 catalog contains messages in the range
BEA2013800 - BEA2013899.
|
BEA-2013800
|
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-2013801
|
Info: Service with name: name has been prepared.
|
Description
| The prepare phase of the OSGI service is complete. |
|
Cause
| Normal operation. |
|
Action
| No action required. |
|
|
BEA-2013802
|
Info: Service with name: name has been activated.
|
Description
| The activation phase of the OSGI service name is complete and is ready for service. |
|
Cause
| Normal operation. |
|
Action
| No action required. |
|
|
BEA-2013803
|
Info: Service with name: name has been deactivated.
|
Description
| The OSGI service name is no longer available. |
|
Cause
| Normal operation. |
|
Action
| No action required. |
|
|
BEA-2013804
|
Error: An exception occurred in a PushManager call-back for client clid. Exception: excp
|
Description
| The PushManager is a service that invokes client client provided call-back methods at the appropriate times. Invocation of one of those call-backs resulted in an exception. |
|
Cause
| Unknown. |
|
Action
| Contact BEA support. For debugging. if the PushManager debug flag is set it will cause a stack trace to be issued whenever this problem occurs. |
|
|
BEA-2013899
|
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. |
|
