Index Changes
View Info

GlassFish ESB Alert Codes and Error Messages

Note - This document is a work in progress.

Contents

GlassFish ESB v2.2 Components


FTP BC Alert Codes


Alert Code Severity Alert Text - Cause - Action
FTPBC-E001036 SEVERE FTPBC-E001036: Cannot get Delivery Channel from context: {0}

Cause: javax.jbi.messaging.MessagingException caught
when initializing and setting MessagingChannel during component start, component not started
Action: Check server log for details and root cause and take appropriate correctional actions
FTPBC-E001037 SEVERE FTPBC-E001037: Failed to start the outbound receiver: {0}

Cause: java.lang.Exception caught
when starting outbound receivers during component start, component not started
Action: Check server log for details and root cause and take appropriate correctional actions
FTPBC-E001038 SEVERE FTPBC-E001038: Failed to start the inbound receiver: {0}

Cause: java.lang.Exception caught
when starting inbound receivers during component start, component not started
Action: Check server log for details and root cause and take appropriate correctional actions
FTPBC-E002001 SEVERE FTPBC-E002001: Failed to deploy service unit due to: {0}

Cause: java.lang.Exception caught
when deploying SU, SU deployment failed.
Action: Depends on the error:
(1) Per Endpoint Persist Store Creation Error:
(1.1)FTPBC uses a local file system directory as the persist store for saving operational data,
such as, recovery logs, persisted sequence files, etc.
per service assembly, per service unit, per endpoint, per operation sub-directories need to be
created, if anything goes wrong due to permission, name conflict, etc. exception will be thrown,
check the file system for permission, entry name conflict etc. and take correctional actions
accordingly.
(1.2) Failed To Register Per Operation CompositeLock - a concurrent control mechanism for clustering support (FTPBC-E002010):
the root cause depends on the underlying persistence used: Database or File System, analyze the root cause the take
correctional actions accordingly.
(2) SU deploy throws Exception:
(2.1) Application Variable Resolution, Application Configuration resolution error
check the corresponding application variable definitions and application configuration definitions on the target application server,
also the tokens in related WSDLs for any undefined applications variables,
application configurations etc. or any mis-match of references and their definitions
(2.2) For other exceptions, analyze further depend on the exception message,
and other releated messages in the server log.
FTPBC-E002002 SEVERE FTPBC-E002002: Failed to initialize service unit {0} due to: {1}

Cause: java.lang.Exception caught
when initializing SU, the corresponding SU deployment or starting failed.
Action: Depends on the error:
(1) Per Endpoint Persist Store Creation Error:
(1.1)FTPBC uses a local file system directory as the persist store for saving operational data,
such as, recovery logs, persisted sequence files, etc.
per service assembly, per service unit, per endpoint, per operation sub-directories need to be
created, if anything goes wrong due to permission, name conflict, etc. exception will be thrown,
check the file system for permission, entry name conflict etc. and take correctional actions
accordingly.
(1.2) Failed To Register Per Operation CompositeLock - a concurrent control mechanism for clustering support (FTPBC-E002010):
the root cause depends on the underlying persistence used: Database or File System, analyze the root cause the take
correctional actions accordingly.
(2) SU initialization throws Exception:
(2.1) Application Variable Resolution, Application Configuration resolution error
check the corresponding application variable definitions and application configuration definitions on the target application server,
also the tokens in related WSDLs for any undefined applications variables,
application configurations etc. or any mis-match of references and their definitions
(2.2) For other exceptions, analyze further depend on the exception message,
and other releated messages in the server log.
FTPBC-E002003 SEVERE FTPBC-E002003: Error starting service unit {0} due to: {1}

Cause: java.lang.Exception caught during SU start, SU start failed
Action:Check exception details and related error messages in server log further to take appropriate action.
FTPBC-E002004 SEVERE FTPBC-E002004: Error stopping service unit {0} due to: {1}

Cause: java.lang.Exception caught during SU stop, SU stop failed
Action:Check exception details and related error messages in server log further to take appropriate action.
FTPBC-E002005 SEVERE FTPBC-E002005: Error shutting down service unit {0} due to: {1}

Cause: java.lang.Exception caught during SU shutdown, SU shutdown failed
Action:Check exception details and related error messages in server log further to take appropriate action.
FTPBC-E002006 SEVERE FTPBC-E002006: Service unit {0} failed pre-processing (inbound endpoint locks registration), an exception was raised. {1}

Cause: java.lang.Exception caught when performing persist store creation and/or composite lock registration during SU start, SU start failed
Action:(1) Per Endpoint Persist Store Creation Error:
(1.1)FTPBC uses a local file system directory as the persist store for saving operational data,
such as, recovery logs, persisted sequence files, etc.
per service assembly, per service unit, per endpoint, per operation sub-directories need to be
created, if anything goes wrong due to permission, name conflict, etc. exception will be thrown,
check the file system for permission, entry name conflict etc. and take correctional actions
accordingly.
(1.2) Failed To Register Per Operation CompositeLock - a concurrent control mechanism for clustering support (FTPBC-E002010):
the root cause depends on the underlying persistence used: Database or File System, analyze the root cause the take
correctional actions accordingly.
(2) For other errors, check the root cause and take correctional action accordingly.
FTPBC-E002008 SEVERE FTPBC-E002008: Service unit {0} failed post-processing after stop (deregister inbound endpoint locks, etc.), an exception was raised. {1}

Cause:
Action:
FTPBC-E002009 SEVERE FTPBC-E002009: Service unit {0} failed post-processing after shutdown (deregister inbound endpoint locks, etc.), an exception was raised. {1}

Cause:
Action:
FTPBC-E004026 SEVERE FTPBC-E004026: Exception when preparing ftp connection parameters for FTP get or poll, servicename={0}, endpoint={1}, e={2}.

Cause:
Action:
FTPBC-E004029 SEVERE FTPBC-E004029: Failed to locate the service endpoint reference for service {0} and endpoint name {1}.

Cause:
Action:
FTPBC-E004030 SEVERE FTPBC-E004030: Failed to send message: {0}

Cause:
Action:
FTPBC-E004033 SEVERE FTPBC-E004033: Inbound message exchange error: status is not DONE, status={0}, message exchange ID={1}

Cause:
Action:
FTPBC-E004041 SEVERE FTPBC-E004041: Unable to resolve endpoint reference for service name {0} and endpoint name {1}.

Cause:
Action:
FTPBC-E004042 SEVERE FTPBC-E004042: Unexpected exception: {0}

Cause:
Action:
FTPBC-E004052 SEVERE FTPBC-E004052: Failed to allocate connection, key = {0}: {1}

Cause:
Action:
FTPBC-E004053 SEVERE FTPBC-E004053: MBeanException caught when try to suspend endpoint (redelivery): serviceName={0}, endpointName={1}, error message={2}.

Cause:
Action:
FTPBC-E004061 SEVERE FTPBC-E004061: Exception when send error during error handling: exception = {0}.

Cause:
Action:
FTPBC-E004067 SEVERE FTPBC-E004067: Exception when create fault during error handling: exception = {0}.

Cause:
Action:
FTPBC-E004068 SEVERE FTPBC-E004068: Exception when applying NM properties to endpoint binding: service unit : {0}, address : {1}, target info : {2}, error : {3}

Cause:
Action:
FTPBC-E004069 SEVERE FTPBC-E004069: Exception when normalizing response message: service unit : {0}, address : {1}, target info : {2}, error : {3}

Cause:
Action:
FTPBC-E004074 SEVERE FTPBC-E004074: {0}::FtpInterface not available, FTP configuration: key = {1}

Cause:
Action:
FTPBC-E004075 SEVERE FTPBC-E004075: {0}::FtpFileClient not available, FTP configuration: key = {1}

Cause:
Action:
FTPBC-E004076 SEVERE FTPBC-E004076: {0}::FtpFileProvider not available, FTP configuration: key = {1}

Cause:
Action:
FTPBC-E004077 SEVERE FTPBC-E004077: Inbound processor aborted, Error validating inbound message exchange properties - {0}

Cause:
Action:
FTPBC-E004078 SEVERE FTPBC-E004078: Thread {0} interrupted when acquiring semaphore: {1}

Cause:
Action:
FTPBC-E004079 SEVERE FTPBC-E004079: Exception when connect, connection key={0}, exception={1}

Cause:
Action:
FTPBC-E004080 SEVERE FTPBC-E004080: Exception returning connection: key={0}, exception={1}

Cause:
Action:
FTPBC-E004084 SEVER FTPBC-E004084: {0}::FtpFileConfiguration not available, FTP configuration: key = {1}

Cause:
Action:
FTPBC-E004088 SEVERE FTPBC-E004088: Error parsing recovery log entry: path = {0} exception = {1}

Cause:
Action:
FTPBC-E004089 SEVERE FTPBC-E004089: Exception processing recovery log entry: messageID = {0} log-path = {1} exception = {2}

Cause:
Action:
FTPBC-E004091 SEVERE FTPBC-E004091: in {0}: calling {1} failed, return text = {2}

Cause:
Action:
FTPBC-E004092 SEVERE FTPBC-E004092: Exception {0} in {1}

Cause:
Action:
FTPBC-E004093 SEVERE FTPBC-E004093: Error when normalizing message (message ID = {0}) in {1}, the message might be malformed, check error log for details, message location: dir = {2}, file = {3}

Cause:
Action:
FTPBC-E004094 SEVERE FTPBC-E004094: Exception when sending message into NMR: service unit : {0}, address : {1}, target info : {2}, error : {3}

Cause:
Action:
FTPBC-R001011 INFO FTPBC-R001011: FTP Binding component {0} shutdown completed.

Cause:
Action:
FTPBC-R001012 INFO FTPBC-R001012: FTP Binding component stopped {0}.

Cause:
Action:
FTPBC-W001004 WARNING FTPBC-W001004: Failed to register status provider MBean.

Cause:
Action:
FTPBC-W001005 WARNING FTPBC-W001005: Failed to register configuration MBean.

Cause:
Action:
FTPBC-W001006 WARNING FTPBC-W001006: Failed to un-register status provider MBean for {0}

Cause:
Action:
FTPBC-W001007 WARNING FTPBC-W001007: Failed to un-register runtime configuration MBean for {0}

Cause:
Action:
FTPBC-W001008 WARNING FTPBC-W001008: Failed to stop the outbound receiver:

Cause:
Action:
FTPBC-W001011 WARNING FTPBC-W001011: Exception when register status mbean, e={0}

Cause:
Action:
FTPBC-W001012 WARNING FTPBC-W001012: Exception when register FTPBC management mbean, e={0}

Cause:
Action:
FTPBC-W004002 WARNING FTPBC-W004002: When messageCorrelate is 'true', inbound message processing expects a matched file name as: {0}<UUID>, but got {1}.

Cause:
Action:
FTPBC-W004011 WARNING FTPBC-W004011: Failed processing one-way inbound messages, exception: {0}.

Cause:
Action:
FTPBC-W004012 WARNING FTPBC-W004012: About to suspend endpoint: serviceName={0}, endpointName={1}.

Cause:
Action:
FTPBC-W004013 WARNING FTPBC-W004013: Can not locate recovery log for message ID = {0}, path= {1}, serviceName={2}, endpointName={3}.

Cause:
Action:



Previous Next

Return to the GlassFish Documentation Home Page
G'day, Anonymous Guest

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