Index Changes

Difference between version and version     

Back to JBI Runtime Management Messages, or JBI Runtime Management Messages Info


At line 1 added 46 lines.
!!GlassFish ESB Alert Codes and Error Messages
__Note -__ This document is a work in progress.\\
\\
__Contents__
* [Glass Fish ESB Alert Codes And Error Messages]
* [BPEL SE Alert Codes]
* [Data Mashup SE Alert Codes]
* [IEP SE Alert Codes]
* [Java EE SE Alert Codes]
* [XSLT SE Alert Codes]
* [Database BC Alert Codes]
* [File BC Alert Codes]
* [FTP BC Alert Codes]
* [HTTP BC Alert Codes]
* [JMS BC Alert Codes]
* [LDAP BC Alert Codes]
* [Scheduler BC Alert Codes]
* [XSLT SE Logging Codes]
** [TransformSL Logging Codes]
* [FTP BC Logging Codes]
* [Scheduler BC Logging Codes]
* [Component Toolkit Logging Codes]
* [Common Utility Logging Codes]
* [Quality of Service (QoS) Logging Codes]
* [JBI Runtime Error Messages|JBIRuntimeMessages]
** [JBI Runtime Framework Messages] (prefixed with __JBIFWxxxx__)
** [JBI Runtime NMR Messages] (prefixed with __JBIMRxxxx__)
** __JBI Runtime Management Messages__ (prefixed with __JBIMA0xxx__, __JBIMA15xx__, __JBIMA16xx__, __JBIMA17xx__, __JBIMA19xx__, __JBIMA2xxx__)
** [JBI Runtime Management Facade Messages] (prefixed with __JBIMA10xx__, __JBIMA13xx__, __JBIMA14xx__, __JBIMA18xx__)
** [JBI Runtime Application Verifier Messages] (prefixed with __JBIMA106x__, __JBIMA107x__, __JBIMA60xx__)
** [JBI Runtime Common Client Messages] (prefixed with __UICMNxxxx__)
** [JBI Runtime Utility Messages] (prefixed with __JBIUTxxxx__)
** [JBI Runtime CLI Messages] (prefixed with __CLIxxx__)
** [JBI Runtime Upgrade Tool Messages] (prefixed with __JBIUGxxx__)
GlassFish ESB v2.2 Components
* [Email BC Logging Codes]
* [HL7 Encoder Logging Codes]
* [POJO SE Logging Codes]
* [HL7BC Alert Codes]
* [REST BC Logging Codes]\\
\\
!!! JBI Runtime Management Messages
At line 92 changed 4 lines.
| __JBIMA0603__ | __NOT USED__ | __ getComponentLoggerMBeanByName: Lookup failed for "{0}".__ \\ \\__Cause__:  \\__Action__:  | LS_GETCOMPONENTLOGGERMBEANBYNAME_LOOKUP_FAILED
| __JBIMA0604__ | __NOT USED__ | __ getSystemLoggerMBean: Lookup failed for "{0}".__ \\ \\__Cause__:  \\__Action__:  | LS_GETSYSTEMLOGGERMBEAN_LOOKUP_FAILED
| __JBIMA0605__ | __NOT USED__ | __ getSystemLoggerMBeans: NO SYSTEM SERVICE LOGGER MBEANS.__ \\ \\__Cause__:  \\__Action__:  | LS_GETSYSTEMLOGGERMBEANS_NO_SERVICES
| __JBIMA0606__ | __NOT USED__ | __ getSystemLoggerMBean: too many mbeans returned by query "{0}".__ \\ \\__Cause__:  \\__Action__:  | LS_GETSYSTEMLOGGERMBEAN_TOO_MANY_MBEANS
| __JBIMA0604__ | WARNING | __ getSystemLoggerMBean: Lookup failed for "{0}".__ \\ \\__Cause__:Failed to lookup a Logger MBean for a particular service.  \\__Action__:Check the server.log for any MBean registration errors.  | LS_GETSYSTEMLOGGERMBEAN_LOOKUP_FAILED
| __JBIMA0605__ | WARNING | __ getSystemLoggerMBeans: NO SYSTEM SERVICE LOGGER MBEANS.__ \\ \\__Cause__:Failed to lookup a Logger MBean for any system service.  \\__Action__:Check the server.log for any MBean registration errors.  | LS_GETSYSTEMLOGGERMBEANS_NO_SERVICES
| __JBIMA0606__ | WARNING | __ getSystemLoggerMBean: too many mbeans returned by query "{0}".__ \\ \\__Cause__:More than one Logger MBean is registered for a system service.  \\__Action__:There might be orphan MBeans, check for orphan server instances and eliminate them.  | LS_GETSYSTEMLOGGERMBEAN_TOO_MANY_MBEANS
At line 165 changed 3 lines.
| __JBIMA1514__ | | __ The changes made to the registry are invalid, the changes will not be serialized to the XML file.__ \\ \\__Cause__:  \\__Action__:  | JBI_ADMIN_INVALID_REGISTRY_OBJECT
| __JBIMA1515__ | | __ Failed to serialize the registry. Error details {0}.__ \\ \\__Cause__:  \\__Action__:  | JBI_ADMIN_FAILED_SERIALIZE_REGISTRY
| __JBIMA1516__ | | __ Failed to initialize the JAXB Context. Error details : {0}__ \\ \\__Cause__:  \\__Action__:  | JBI_ADMIN_FAILED_JAXB_INIT
| __JBIMA1514__ | SEVERE | __ The changes made to the registry are invalid, the changes will not be serialized to the XML file.__ \\ \\__Cause__:The updates made to the registry make it invalid.  \\__Action__:This is a rare secnario, call Sun support if you encounter this issue.  | JBI_ADMIN_INVALID_REGISTRY_OBJECT
| __JBIMA1515__ | SEVERE | __ Failed to serialize the registry. Error details {0}.__ \\ \\__Cause__:Changes to the registry ( hence system state ) could not be persisted. Exact cause is included in the message.  \\__Action__:Try to resolve the issue if possible, else contact Sun support.  | JBI_ADMIN_FAILED_SERIALIZE_REGISTRY
| __JBIMA1516__ | SEVERE | __ Failed to initialize the JAXB Context. Error details : {0}__ \\ \\__Cause__:Registry initialization failed, exact cause is included in the message.  \\__Action__:Try to resolve the issue if possible, else contact Sun support  | JBI_ADMIN_FAILED_JAXB_INIT
At line 251 removed 1 line.
| __JBIMA2100 THIS IS A DUPLICATE __ | | __ JavaEEDeployer MBean not registered: {0}__ \\ \\__Cause__:  \\__Action__:  | JBI_ADMIN_NO_JAVAEEDEPLOYER_MBEAN
At line 265 changed 1 line.
| __JBIMA3100__ | SEVERE |__JavaEEDeployer MBean not registered: {0}__ \\ \\ __Cause:__To deploy service units to the JavaEE SE it's deployer MBean is used, the runtime cannont find this MBean. \\ __Action:__Check the server.log for errors related to MBean registration. |JBI_ADMIN_NO_JAVAEEDEPLOYER_MBEAN = :
| __JBIMA3100__ | SEVERE |__JavaEEDeployer MBean not registered: {0}__ \\ \\ __Cause:__To deploy service units to the JavaEE SE it's deployer MBean is used, the runtime cannont find this MBean. \\ __Action:__Check the server.log for errors related to MBean registration. |JBI_ADMIN_NO_JAVAEEDEPLOYER_MBEAN
At line 267 changed 2 lines.
!!Related Links:
* [JBI Runtime Messages]
\\
\\
[Previous|JBIRuntimeNMRMessages] [Next|JBIRuntimeManagementFacadeMessages]

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-45) was last changed on 10-Feb-10 19:51 PM, -0800 by CarolT