test

JBI Component Alert Codes and Error Messages

FTP Binding Component Alert Codes

The following table lists each alert code generated by the FTP Binding Component and describes the cause of the alert along with the recommended action for you to take.

Alert Code 

Severity 

Alert Text, Cause, and Action 

FTPBC-E001036 

Severe 

Cannot get Delivery Channel from context: {0} 

Cause: The exception javax.jbi.messaging.MessagingException was caught when initializing and setting the messaging channel during component startup. The component is not started.

Action: Check the server log for details and the root cause to determine the action to take.

FTPBC-E001037  

Severe 

Failed to start the outbound receiver: {0} 

Cause: The exception java.lang.Exception was caught when starting outbound receivers during component startup. The component was not started.

Action: Check the server log for details and the root cause to determine the action to take.

FTPBC-E001038 

Severe 

Failed to start the inbound receiver: {0} 

Cause: The exception java.lang.Exception was caught when starting inbound receivers during component startup. The component was not started.

Action: Check the server log for details and the root cause to determine the action to take.

FTPBC-E002001  

Severe 

Failed to deploy service unit due to: {0} 

Cause: The exception java.lang.Exception was caught when deploying the service unit, and deployment failed.

Action: The action to take depends on the error:

  1. Per endpoint persist store creation error:

    • The FTP BC uses a local file system directory as the persistence location for saving operational data, such as recovery logs, persisted sequence files, and so on. Subdirectories are created per Service Assembly, per service unit, per endpoint, and per operation. If anything goes wrong due to permission, name conflict, and so on, this exception will be thrown. Check the file system for permission, entry name conflict, and correct the error.

    • Failed to register per operation composite lock:

      The lock is 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 and correct the error.

  2. Service unit deployment throws the exception:

    • Application variable resolution:

      For this error, check the corresponding application variable definitions and application configuration definitions on the target application serve. Check the tokens in related WSDL documents for any undefined application variables, application configurations, and so on. Also check for any mismatch of references and their definitions .

    • Other exceptions:

      Analyze the exception message and other related messages in the server log to determine the action to take.

FTPBC-E002002 

Severe 

Failed to initialize service unit {0} due to: {1}  

Cause: A java.lang.Exception was caught when initializing the service unit, and the corresponding service unit deployment or startup failed.

Action: The action to take depends on the error:

  1. Per endpoint persist store creation error:

    • The FTP BC uses a local file system directory as the persistence location for saving operational data, such as recovery logs, persisted sequence files, and so on. Subdirectories need to be created per Service Assembly, per service unit, per endpoint, and per operation. If anything goes wrong due to permissions, name conflict, and so on, an exception is thrown. Check the file system for permissions, entry name conflict, and so on, and make the needed corrections.

    • Failed to register per operation composite lock:

      The lock is 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 to determine the action to take.

  2. Service unit initialization throws the exception:

    • Application variable resolution:

      For this error, check the corresponding application variable definitions and application configuration definitions on the target application server. Check the tokens in related WSDL documents for any undefined application variables, application configurations, and so on. Also check for any mismatch of references and their definitions.

    • Other exceptions;

      Analyze the exception message and other related messages in the server log to determine the action to take.

FTPBC-E002003  

Severe 

Error starting service unit {0} due to: {1} 

Cause: The exception java.lang.Exception caught during service unit startup, and the startup failed.

Action: Check exception details and related error messages in the server log to determine the action to take.

FTPBC-E002004 

Severe 

Error stopping service unit {0} due to: {1} 

Cause: The exception java.lang.Exception caught while stopping the service unit, and the stop process failed.

Action: Check exception details and related error messages in the server log to determine the action to take.

FTPBC-E002005  

Severe 

Error shutting down service unit {0} due to: {1} 

Cause: The exception java.lang.Exception was 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 

Service unit {0} failed pre-processing (inbound endpoint locks registration), an exception was raised. {1} 

Cause: The exception java.lang.Exception was caught when creating the persistence store or registering the composite lock during service unit startup, and the startup failed.

Action: The action to take depends on the type of error:

  1. Per endpoint persist store creation error:

    • The FTP BC uses a local file system directory as the persistence location for saving operational data, such as recovery logs, persisted sequence files, and so on. Subdirectories are created per Service Assembly, per service unit, per endpoint, and per operation. If anything goes wrong due to permission, name conflict, and so on, this exception will be thrown. Check the file system for permission, entry name conflict, and correct the error.

    • Failed to register per operation composite lock:

      The lock is 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 and correct the error.

  2. Other exceptions:

    Analyze the exception message and other related messages in the server log to determine the action to take.

FTPBC-E002008  

Severe 

Service unit {0} failed post-processing after stop (deregister inbound endpoint locks, etc.), an exception was raised. {1} 

FTPBC-E002009 

Severe 

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

FTPBC-E004026 

Severe 

Exception when preparing ftp connection parameters for FTP get or poll, servicename={0}, endpoint={1}, e={2}. 

FTPBC-E004029  

Severe 

Failed to locate the service endpoint reference for service {0} and endpoint name {1}. 

FTPBC-E004030  

Severe 

Failed to send message: {0} 

FTPBC-E004033  

Severe 

Inbound message exchange error: status is not DONE, status={0}, message exchange ID={1} 

FTPBC-E004041 

Severe 

Unable to resolve endpoint reference for service name {0} and endpoint name {1}. 

FTPBC-E004042  

Severe 

Unexpected exception: {0} 

FTPBC-E004052  

Severe 

Failed to allocate connection, key = {0}: {1} 

FTPBC-E004053  

Severe 

MBeanException caught when try to suspend endpoint (redelivery): serviceName={0}, endpointName={1}, error message={2}. 

FTPBC-E004061  

Severe 

Exception when send error during error handling: exception = {0}. 

FTPBC-E004067  

Severe 

Exception when create fault during error handling: exception = {0}. 

FTPBC-E004068  

Severe 

Exception when applying NM properties to endpoint binding: service unit : {0}, address : {1}, target info : {2}, error : {3} 

FTPBC-E004069  

Severe 

Exception when normalizing response message: service unit : {0}, address : {1}, target info : {2}, error : {3} 

FTPBC-E004074  

Severe 

{0}::FtpInterface not available, FTP configuration: key = {1} 

FTPBC-E004075  

Severe 

{0}::FtpFileClient not available, FTP configuration: key = {1} 

FTPBC-E004076  

Severe 

{0}::FtpFileProvider not available, FTP configuration: key = {1} 

FTPBC-E004077  

Severe 

Inbound processor aborted, Error validating inbound message exchange properties - {0} 

FTPBC-E004078 

Severe 

Thread {0} interrupted when acquiring semaphore: {1} 

FTPBC-E004079 

Severe 

Exception when connect, connection key={0}, exception={1} 

FTPBC-E004080  

Severe 

Exception returning connection: key={0}, exception={1} 

FTPBC-E004084  

Severe 

{0}::FtpFileConfiguration not available, FTP configuration: key = {1} 

FTPBC-E004088  

Severe 

Error parsing recovery log entry: path = {0} exception = {1} 

FTPBC-E004089 

Severe 

Exception processing recovery log entry: messageID = {0} log-path = {1} exception = {2} 

FTPBC-E004091 

Severe 

in {0}: calling {1} failed, return text = {2} 

FTPBC-E004092 

Severe 

Exception {0} in {1} 

FTPBC-E004093 

Severe 

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} 

FTPBC-E004094 

Severe 

Exception when sending message into NMR: service unit : {0}, address : {1}, target info : {2}, error : {3} 

FTPBC-R001011  

Info 

FTP Binding component {0} shutdown completed. 

FTPBC-R001012  

Info 

FTP Binding component stopped {0}. 

FTPBC-W001004 

Warning 

Failed to register status provider MBean. 

FTPBC-W001005 

Warning 

Failed to register configuration MBean. 

FTPBC-W001006  

Warning 

Failed to un-register status provider MBean for {0} 

FTPBC-W001007 

Warning 

Failed to un-register runtime configuration MBean for {0} 

FTPBC-W001008  

Warning 

Failed to stop the outbound receiver:  

FTPBC-W001011 

Warning 

Exception when register status mbean, e={0} 

FTPBC-W001012  

Warning 

Exception when register FTPBC management mbean, e={0} 

FTPBC-W004002  

Warning 

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

FTPBC-W004011  

Warning 

Failed processing one-way inbound messages, exception: {0}. 

FTPBC-W004012  

Warning 

About to suspend endpoint: serviceName={0}, endpointName={1}. 

FTPBC-W004013 

Warning 

Can not locate recovery log for message ID = {0}, path= {1}, serviceName={2}, endpointName={3}.