The MBeanTypingUtil1.0 catalog contains messages in the range
BEA-2012300 - BEA-2012399. Messages in this catalog are part of the
com.bea.adaptive.mbean.typing
Internationalization package and the com.bea.adaptive.mbean.typing Localization package.
|
BEA-2012300
|
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-2012301
|
Info: Processing count MBeans.
|
Description
| The MBeanTypeUtility is downloading count MBean definitions from the MBeanServer. |
|
Cause
| Normal operation. |
|
Action
| No action required. |
|
|
BEA-2012302
|
Info: All MBeans have been processed.
|
Description
| The MBeanTypeUtility has downloaded al currently known MBean definitions from the MBeanServer. |
|
Cause
| Normal operation. |
|
Action
| No action required. |
|
|
BEA-2012303
|
Error: The MBeanTypeUtility cannot process MBean instance due to excp excp on MBeanServer: mBeanServer and MBean: mbean --- Retrying once...
|
Description
| The MBeanTypeUtility has failed in trying to access a registered MBean. One retry attempt will be made. If that fails the MBean will be skipped. |
|
Cause
| Internal error. |
|
Action
| Contact Oracle support. |
|
|
BEA-2012304
|
Error: The MBeanTypeUtility failed a second time to process MBean instance due to excp: excp on MBeanServer: mBeanServer and MBean: mbean --- Skipping this MBean...
|
Description
| The MBeanTypeUtility has failed in two tries to access a registered MBean. The MBean is skipped and processing is attempted to continue. |
|
Cause
| Internal error. |
|
Action
| Contact Oracle support. |
|
|
BEA-2012305
|
Error: The MBeanTypeUtility failed to process two distinct MBeans in a row. The most recent problem was on MBeanServer: mBeanServer and MBean: mBeanServer --- No further MBeans will be processed.
|
Description
| The MBeanTypeUtility has failed in the attempt to access two consecutive different MBeans. It is now assummed that a several error situation exists. No futher MBean retrievals will be attempted after this point. |
|
Cause
| Internal error. |
|
Action
| Contact Oracle support. |
|
|
BEA-2012306
|
Error: messageLabelUnable to process the notifType of MBean: oName due to internal errors. The managed process might be shutting down.
|
Description
| messageLabelThe MBeanTypeUtility has failed while trying to process a notification for an MBean. The MBean notifType is being skipped. MBean: oName. |
|
Cause
| Most likely the process is shutting down, so it is safe to ignore this. |
|
Action
| If the process is known to be active, the user should contact Oracle support to resolve why the MBean cannot be processed. Setting the module debug flag will cause stack traces to be printed. |
|
|
BEA-2012307
|
Warning: messageLabelUnable to process the notifType of MBean: oName due to internal errors. The managed process appears to be shutting down.
|
Description
| messageLabelThe MBeanTypeUtility has failed while trying to process a notification for an MBean. The MBean notifType is being skipped. MBean: oName. |
|
Cause
| Most likely the process is shutting down, so it is safe to ignore this. |
|
Action
| If the process is known to be active, the user may want to contact Oracle support to resolve why the MBean cannot be processed. Setting the module debug flag will cause stack traces to be printed. |
|
|
BEA-2012399
|
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. |
|
