Index Changes

GlassFish ESB Alert Codes and Error Messages

Note - This document is a work in progress.

Contents

GlassFish ESB v2.2 Components


FTP BC Logging Codes

Logging CodeSeverityMessage Text - Cause - Action
FTPBC-W001013 WARNING Can not find inbound message processor associated with key={0}.

Cause:
Action:
FTPBC-C001999 CONFIG FTPBC-C001999: Attribute changed

Cause:
Action:
FTPBC-E001001 SEVERE FTPBC-E001001: Failed to unregister MBean: {0}

Cause:
Action:
FTPBC-E001002 SEVERE FTPBC-E001002: Missing required ftp:transfer 'userDefDirListStyle' and / or 'userDefDirListHeuristics' attribute(value) for ftp operation {0} while 'useUserDefinedHeuristics' is 'true'.

Cause:
Action:
FTPBC-E001003 SEVERE FTPBC-E001003: Invalid FTP Command Channel timeout {0}, should be integer >= 0, operation {1}.

Cause:
Action:
FTPBC-E001004 SEVERE FTPBC-E001004: Invalid FTP Data Channel timeout {0}, should be integer >= 0, operation {1}.

Cause:
Action:
FTPBC-E001005 SEVERE FTPBC-E001005: Missing FTP URL in ftp binding address

Cause:
Action:
FTPBC-E001006 SEVERE FTPBC-E001006: FTP url is still a ftp url placeholder, please specify a concrete FTP address.

Cause:
Action:
FTPBC-E001007 SEVERE FTPBC-E001007: Invalid FTP url, not starting with ftp://, url= {0}

Cause:
Action:
FTPBC-E001008 SEVERE FTPBC-E001008: Invalid FTP url, path not allowed for a url as FTP endpoint, url= {0}

Cause:
Action:
FTPBC-E001009 SEVERE FTPBC-E001009: Malformed FTP url, url= {0}

Cause:
Action:
FTPBC-E001010 SEVERE FTPBC-E001010: Invalid port in URL, must be a positive number following host name as in localhost:21, url= {0}

Cause:
Action:
FTPBC-E001011 SEVERE FTPBC-E001011: Failed to parse XSD file: {0} in the service assembly.

Cause:
Action:
FTPBC-E001011 SEVERE FTPBC-E001011: Invalid FTP url, host required, url= {0}

Cause:
Action:
FTPBC-E001012 SEVERE FTPBC-E001012: Failed to start the end point with service name {0} and endpoint name {1}: {2}

Cause:
Action:
FTPBC-E001012 SEVERE FTPBC-E001012: Invalid FTP port : {0}.

Cause:
Action:
FTPBC-E001013 SEVERE FTPBC-E001013: Failed to start the end point with service name {0} and endpoint name {1}: {2}

Cause:
Action:
FTPBC-E001013 SEVERE FTPBC-E001013: {0} is an invalid token name.

Cause:
Action:
FTPBC-E001014 SEVERE FTPBC-E001014: Attribute value {0} contains an empty migration application variable reference, attribute name = {1}.

Cause:
Action:
FTPBC-E001014 SEVERE FTPBC-E001014: Failed to start inbound message processor for endpoint: {0}.

Cause:
Action:
FTPBC-E001015 SEVERE FTPBC-E001015: Failed deploying SU, ID={0} error={1}

Cause:
Action:
FTPBC-E001015 SEVERE FTPBC-E001015: application variable reference {0} in attribute value {1} (attribute name = {2}) has no definition in MBean configuration parameter "EnvironmentVariables".

Cause:
Action:
FTPBC-E001016 SEVERE FTPBC-E001016: Error : de-referenced application variable has further reference in it, attribute name = {0}, attribute value = {1}, application variable name = {2}, application variable value = {3}.

Cause:
Action:
FTPBC-E001017 SEVERE FTPBC-E001017: Error : attribute still has un-resolved application variable reference, attribute value {0}, attribute name = {1}

Cause:
Action:
FTPBC-E001018 SEVERE FTPBC-E001018: Mandatory messageRepository not specified.

Cause:
Action:
FTPBC-E001019 SEVERE FTPBC-E001019: Missing required ftp:transfer 'encodingStyle' attribute(value) for ftp operation {0} while 'use' is 'encoded'.

Cause:
Action:
FTPBC-E001020 SEVERE FTPBC-E001020: Invalid message name prefix {0}, should not contain name pattern escape char '%', operation {1}.

Cause:
Action:
FTPBC-E001021 SEVERE FTPBC-E001021: Both sendTo and receiveFrom for ftp:transfer not specified.

Cause:
Action:
FTPBC-E001022 SEVERE FTPBC-E001022: Missing required ftp:transfer 'encodingStyle' attribute(value) for ftp operation {0} while 'use' is 'encoded'.

Cause:
Action:
FTPBC-E001023 SEVERE FTPBC-E001023: Attribute {0} requires a path pointing to a file instead of path={1}.

Cause:
Action:
FTPBC-E001024 SEVERE FTPBC-E001024: Pre/Post operation RENAME or COPY configured with no corresponding destination specified.

Cause:
Action:
FTPBC-E001025 SEVERE FTPBC-E001025: Invalid polling interval for inbound {0}, should be integer > 0.

Cause:
Action:
FTPBC-E001026 SEVERE FTPBC-E001026: Missing proxy URL in ftp binding address

Cause:
Action:
FTPBC-E001027 SEVERE FTPBC-E001027: Proxy url is still a placeholder, please specify a concrete proxy address.

Cause:
Action:
FTPBC-E001028 SEVERE FTPBC-E001028: Malformed proxy url, url=

Cause:
Action:
FTPBC-E001029 SEVERE FTPBC-E001029: Invalid proxy url, path not allowed for a proxy url

Cause:
Action:
FTPBC-E001030 SEVERE FTPBC-E001030: Invalid proxy url, host required, url= {0}

Cause:
Action:
FTPBC-E001031 SEVERE FTPBC-E001031: No proxy host specified when 'useProxy' is set to 'true'.

Cause:
Action:
FTPBC-E001032 SEVERE FTPBC-E001032: Invalid Proxy port : {0}.

Cause:
Action:
FTPBC-E001033 SEVERE FTPBC-E001033: Invalid proxy protocol {0}, valid proxy protocols are socks4, socks5.

Cause:
Action:
FTPBC-E001034 SEVERE FTPBC-E001034: Missing proxy protocol scheme in proxy URL : {0}.

Cause:
Action:
FTPBC-E001035 SEVERE FTPBC-E001035: Component Context is null.

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

Cause:
Action:
FTPBC-E001037 SEVERE FTPBC-E001037: Failed to start the outbound receiver: {0}

Cause:
Action:
FTPBC-E001038 SEVERE FTPBC-E001038: Failed to start the inbound receiver: {0}

Cause:
Action:
FTPBC-E001039 SEVERE FTPBC-E001039: Invalid argument for setting attribute {0}: {1}

Cause:
Action:
FTPBC-E001040 SEVERE FTPBC-E001040: A value of {0} is not valid for attribute {1}. The valid range is {2} - {3}.

Cause:
Action:
FTPBC-E001047 SEVERE FTPBC-E001047: property name is NULL when setting configuration parameters.

Cause:
Action:
FTPBC-E001048 SEVERE FTPBC-E001048: property value is NULL when setting configuration parameters, name={0}.

Cause:
Action:
FTPBC-E001049 SEVERE FTPBC-E001049: Invalid endpoint name: {0}.

Cause:
Action:
FTPBC-E001050 SEVERE FTPBC-E001050: Failed to suspend endpoint: {0}.

Cause:
Action:
FTPBC-E001051 SEVERE FTPBC-E001051: Failed to resume endpoint: {0}.

Cause:
Action:
FTPBC-E001052 SEVERE FTPBC-E001052: When SecuredFTP is : {0}, keystore information is required, validation failed for {1}.

Cause:
Action:
FTPBC-E002001 SEVERE FTPBC-E002001: Failed to deploy service unit due to: {0}

Cause:
Action:
FTPBC-E002002 SEVERE FTPBC-E002002: Failed to initialize service unit {0} due to: {1}

Cause:
Action:
FTPBC-E002003 SEVERE FTPBC-E002003: Error starting service unit {0} due to: {1}

Cause:
Action:
FTPBC-E002004 SEVERE FTPBC-E002004: Error stopping service unit {0} due to: {1}

Cause:
Action:
FTPBC-E002005 SEVERE FTPBC-E002005: Error shutting down service unit {0} due to: {1}

Cause:
Action:
FTPBC-E002006 SEVERE FTPBC-E002006: Service unit {0} failed pre-processing (inbound endpoint locks registration), an exception was raised. {1}

Cause:
Action:
FTPBC-E002007 SEVERE FTPBC-E002007: Exception caught when de-register EPs from inbound EP lock registry, e={0}

Cause:
Action:
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-E003001 SEVERE FTPBC-E003001: Missing ftp:address in wsdl for this service {0}.

Cause:
Action:
FTPBC-E003002 SEVERE FTPBC-E003002: Missing ftp:operation definition(s) in wsdl for this service {0}.

Cause:
Action:
FTPBC-E003003 SEVERE FTPBC-E003003: Missing required Input properties for ftp binding operation {0}.

Cause:
Action:
FTPBC-E003004 SEVERE FTPBC-E003004: Missing required <ftp:transfer>/<ftp:message> for ftp binding operation {0}.

Cause:
Action:
FTPBC-E003005 SEVERE FTPBC-E003005: Missing required 'encodingStyle' (in <ftp:transfer>/<ftp:message>) for ftp binding operation {0} while 'use' is 'encoded'.

Cause:
Action:
FTPBC-E003006 SEVERE FTPBC-E003006: Missing required Output properties for ftp binding operation {0}.

Cause:
Action:
FTPBC-E004001 SEVERE FTPBC-E004001: Invalid FTP port : {0}.

Cause:
Action:
FTPBC-E004002 SEVERE FTPBC-E004002: No proxy host specified when 'useProxy' is set to 'true'.

Cause:
Action:
FTPBC-E004003 SEVERE FTPBC-E004003: Invalid proxy protocol {0}, valid proxy protocols are socks4, socks5.

Cause:
Action:
FTPBC-E004004 SEVERE FTPBC-E004004: Missing FTP target file, operation = {0}.

Cause:
Action:
FTPBC-E004005 SEVERE FTPBC-E004005: Invalid ftp target spec, should be in the form of path/filename, spec={0}, operation={1}

Cause:
Action:
FTPBC-E004006 SEVERE FTPBC-E004006: No PreSendLocation specified when PreSendCommand is {0}.

Cause:
Action:
FTPBC-E004007 SEVERE FTPBC-E004007: No directory name found in PreSendLocation {0}, when PreSendCommand is RENAME or COPY.

Cause:
Action:
FTPBC-E004008 SEVERE FTPBC-E004008: No file name found in PreSendLocation {0} when PostSendCommand is RENAME or COPY.

Cause:
Action:
FTPBC-E004009 SEVERE FTPBC-E004009: No PostSendLocation specified when PostSendCommand is {0}.

Cause:
Action:
FTPBC-E004010 SEVERE FTPBC-E004010: No directory name found in PostSendLocation {0} when PostSendCommand is RENAME or DELETE.

Cause:
Action:
FTPBC-E004011 SEVERE FTPBC-E004011: No file name found in PostSendLocation {0} when PostSendCommand is RENAME or DELETE.

Cause:
Action:
FTPBC-E004012 SEVERE FTPBC-E004012: Missing messageRepository - a path pointing to a remote directory where message transfer occurs.

Cause:
Action:
FTPBC-E004013 SEVERE FTPBC-E004013: Message tag instance {0} not starting with UUID, messageName={1}, operation={2}.

Cause:
Action:
FTPBC-E004014 SEVERE FTPBC-E004014: Invalid UUID instance {0}, length < 36, messageName={1}, operaiton={2}.

Cause:
Action:
FTPBC-E004015 SEVERE FTPBC-E004015: Attribute messageName {0} does not start with %u, while UUID instance {1} is provided to substitute UUID symbol, operation = {2}.

Cause:
Action:
FTPBC-E004016 SEVERE FTPBC-E004016: Invalid extensibility element : {0}

Cause:
Action:
FTPBC-E004017 SEVERE FTPBC-E004017: No UUID available when a consumer is polling response with message correlate enabled.

Cause:
Action:
FTPBC-E004018 SEVERE FTPBC-E004018: No PreReceiveLocation specified when PreReceiveCommand is {0}.

Cause:
Action:
FTPBC-E004019 SEVERE FTPBC-E004019: No directory name found in PreReceiveLocation {0}, when PreReceiveCommand is RENAME or COPY.

Cause:
Action:
FTPBC-E004020 SEVERE FTPBC-E004020: No file name found in PreReceiveLocation {0} when PostSendCommand is RENAME or COPY.

Cause:
Action:
FTPBC-E004021 SEVERE FTPBC-E004021: No PostReceiveLocation specified when PostReceiveCommand is {0}.

Cause:
Action:
FTPBC-E004022 SEVERE FTPBC-E004022: No directory name found in PostReceiveLocation {0} when PostReceiveCommand is RENAME or DELETE.

Cause:
Action:
FTPBC-E004023 SEVERE FTPBC-E004023: No file name found in PostReceiveLocation {0} when PostReceiveCommand is RENAME or DELETE.

Cause:
Action:
FTPBC-E004024 SEVERE FTPBC-E004024: Missing stage directory, operation {0}.

Cause:
Action:
FTPBC-E004025 SEVERE FTPBC-E004025: Missing stage file, operation {0}.

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-E004031 SEVERE FTPBC-E004031: Encountered an invalid inbound message: null.

Cause:
Action:
FTPBC-E004032 SEVERE FTPBC-E004032: Encountered an invalid message exchange pattern of {0} while processing the message exchange reply status.

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

Cause:
Action:
FTPBC-E004034 SEVERE FTPBC-E004034: Encountered an invalid message exchange id of {0} while processing the message exchange reply status.

Cause:
Action:
FTPBC-E004035 SEVERE FTPBC-E004035: Invalid message exchange pattern for ftp operation {0}.

Cause:
Action:
FTPBC-E004036 SEVERE FTPBC-E004036: Missing required Input properties for inbound ftp operation {0}.

Cause:
Action:
FTPBC-E004037 SEVERE FTPBC-E004037: Missing required <ftp:transfer>/<ftp:message> properties for inbound ftp operation {0}.

Cause:
Action:
FTPBC-E004038 SEVERE FTPBC-E004038: Invalid child element found for \<input>, expecting <ftp:transfer>/<ftp:message> for inbound ftp operation {0}.

Cause:
Action:
FTPBC-E004039 SEVERE FTPBC-E004039: Missing required Output properties for request-response type inbound ftp operation {0}.

Cause:
Action:
FTPBC-E004040 SEVERE FTPBC-E004040: Invalid child element found for <output>, expecting <ftp:transfer>/<ftp:message> for inbound ftp operation {0}.

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-E004043 SEVERE FTPBC-E004043: Missing required Output properties for inbound ftp operation {0}.

Cause:
Action:
FTPBC-E004044 SEVERE FTPBC-E004044: Missing required ftp:transfer element for inbound ftp operation {0}.

Cause:
Action:
FTPBC-E004045 SEVERE FTPBC-E004045: Missing required Input properties for outbound ftp operation {0}.

Cause:
Action:
FTPBC-E004046 SEVERE FTPBC-E004046: Missing required ftp:transfer element for outbound ftp operation {0}.

Cause:
Action:
FTPBC-E004048 SEVERE FTPBC-E004048: Missing required Output properties for polling response for ftp operation {0}.

Cause:
Action:
FTPBC-E004049 SEVERE FTPBC-E004049: Missing required extensibility element <ftp:transfer>/<ftp:message> element for polling response for ftp operation {0}.

Cause:
Action:
FTPBC-E004051 SEVERE FTPBC-E004051: 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-E004054 SEVERE FTPBC-E004054: %p representing current target directory should not appear in Pre/Post operation's target file name pattern : {0}

Cause:
Action:
FTPBC-E004060 SEVERE FTPBC-E004060: Failed to write message: ServiceUnit ID : {0}, address : {1}, destination : {2}, exception : {3}

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

Cause:
Action:
FTPBC-E004062 SEVERE FTPBC-E004062: FTPBC Runtime validation error: service unit : {0}, address : {1}, target info : {2}, error : {3}

Cause:
Action:
FTPBC-E004063 SEVERE FTPBC-E004063: FTP connection error: connection key: {0}, exception : {1}

Cause:
Action:
FTPBC-E004065 SEVERE FTPBC-E004065: Error retrieving FTP target file: connection key : {0}, target file : {1}, exception : {2}

Cause:
Action:
FTPBC-E004066 SEVERE FTPBC-E004066: Error when instatiating and starting response poller in synchronized request response processing \n

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-E004070 SEVERE FTPBC-E004070: Exception when instantiate response poller: service unit : {0}, address : {1}, target info : {2}, error : {3}

Cause:
Action:
FTPBC-E004071 SEVERE FTPBC-E004071: Exception when schedule response poller timeout : service unit : {0}, address : {1}, target info : {2}, response poller timeout : {3}, error : {3}

Cause:
Action:
FTPBC-E004072 SEVERE FTPBC-E004072: Exception when configuring response poller : service unit : {0}, address : {1}, target info : {2}, error : {3}

Cause:
Action:
FTPBC-E004073 SEVERE FTPBC-E004073: Exception when getting connection from pool : service unit : {0}, address : {1}, target info : {2}, connection key : {3}, error : {4}

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-E004081 SEVERE FTPBC-E004081: can not resolve destination for pre transfer operation {0}, thread {1}, PreDirectoryName = {2}, PreDirectoryNameIsPattern = {3}, PreFileName = {4}, PreFileNameIsPattern = {5}.

Cause:
Action:
FTPBC-E004082 SEVERE FTPBC-E004082: Error when completing pending FTP command at the end of retrieving remote file, return code = {0}, return text = {1}.

Cause:
Action:
FTPBC-E004083 SEVERE FTPBC-E004083: Failed to mkdir: dir = {0}, FTP return code = {1}, return text = {2}.

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

Cause:
Action:
FTPBC-E004085 SEVERE FTPBC-E004085: Failed to put file: dir = {0}, file = {1}, FTP return code = {2}, return text = {3}.

Cause:
Action:
FTPBC-E004086 SEVERE FTPBC-E004086: Failed to move stage file to target directory: stage dir = {0}, stage file = {1}, target dir = {2}, target file = {3}, FTP return code = {4}, return text = {5}.

Cause:
Action:
FTPBC-E004087 SEVERE FTPBC-E004087: Malformed recovery log entry: expected prefix = {0} line={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-E004090 SEVERE FTPBC-E004090: Exception when saving info regarding a malformed message or payload during {0}: message exchange ID = {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-E004095 SEVERE FTPBC-E004095: in {0}: calling {1} failed, return text = {2}

Cause:
Action:
FTPBC-E005001 SEVERE FTPBC-E005001: Encountered an invalid binding operation name '{0}' for FTP BC.

Cause:
Action:
FTPBC-E005002 SEVERE FTPBC-E005002: Encountered invalid message exchange pattern for FTP BC operation '{0}'.

Cause:
Action:
FTPBC-E005003 SEVERE FTPBC-E005003: Encountered invalid message type definition for FTP BC operation '{0}'.

Cause:
Action:
FTPBC-E005004 SEVERE FTPBC-E005004: Can not find the encoder while processing encoded data - denormalization : message part = {0}, use = {1}, encodingStyle = {2}.

Cause:
Action:
FTPBC-E005005 SEVERE FTPBC-E005005: Exception when creating wrapper builder in FTPNormalizer, e={0}

Cause:
Action:
FTPBC-E005006 SEVERE FTPBC-E005006: Exception when creating doc builder in FTPNormalizer, e={0}

Cause:
Action:
FTPBC-E005007 SEVERE FTPBC-E005007: Exception when creating transformer in FTPNormalizer, e={0}

Cause:
Action:
FTPBC-E005008 SEVERE FTPBC-E005008: Encountered invalid message type definition for FTP BC operation '{0}'.

Cause:
Action:
FTPBC-E005010 SEVERE FTPBC-E005010: Can not find the encoder while processing encoded data - normalization : message part = {0}, use = {1}, encodingStyle = {2}.

Cause:
Action:
FTPBC-E005011 SEVERE FTPBC-E005011: Error occured while transforming the normalized message: {0}

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

Cause:
Action:
FTPBC-E006002 SEVERE FTPBC-E006002: doRawCommands(): ftp raw command {0} failed - reason text = {1};

Cause:
Action:
FTPBC-E006003 SEVERE FTPBC-E006003: doRawCommands(): ftp raw command {0} failed - exception = {1};

Cause:
Action:
FTPBC-E006004 SEVERE FTPBC-E006004: configureSocks(): Invalid configuration parameters - No SOCKS

Cause:
Action:
FTPBC-E006005 SEVERE FTPBC-E006005: open(): provider.connect() failed - return text = {0}

Cause:
Action:
FTPBC-E006006 SEVERE FTPBC-E006006: open(): provider.login() failed - return text = {0}

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

Cause:
Action:
FTPBC-E006008 SEVERE FTPBC-E006008: in {0}: Invalid command {1} used

Cause:
Action:
FTPBC-E006009 SEVERE FTPBC-E006009: in {0} : Failed to create destination directory {1}

Cause:
Action:
FTPBC-E006010 SEVERE FTPBC-E006010: in {0} : output stream already exists

Cause:
Action:
FTPBC-E006011 SEVERE FTPBC-E006011: in {0} : Failed to create working directory {1}

Cause:
Action:
FTPBC-E006012 SEVERE FTPBC-E006012: in {0} : input stream already exists

Cause:
Action:
FTPBC-E006013 SEVERE FTPBC-E006013: No connection is available. The ConnectionEstablishmentMode is {0}

Cause:
Action:
FTPBC-E006014 SEVERE FTPBC-E006014: No connection is available. connection mode is {0}, the connection may have timed out, call connect()

Cause:
Action:
FTPBC-E006015 SEVERE FTPBC-E006015: in {0} : Exception when saving persistent state, e={1}

Cause:
Action:
FTPBC-E006016 SEVERE FTPBC-E006016: in {0} : Exception when resolving target file.

Cause:
Action:
FTPBC-E006017 SEVERE FTPBC-E006017: in {0} : Missing directory listing style

Cause:
Action:
FTPBC-E006018 SEVERE FTPBC-E006018: Failed to update heuristics using directory listing style {0}. Got exception {1}

Cause:
Action:
FTPBC-E006019 SEVERE FTPBC-E006019: Missing user defined heuristics configuration file when setting user defined directory listing style {0}

Cause:
Action:
FTPBC-E006020 SEVERE FTPBC-E006020: in {0} : Failed to update heuristics using user defined directory listing style {1}. Got exception {2}

Cause:
Action:
FTPBC-E006021 SEVERE FTPBC-E006021: Missing or invalid parameter {0}, value {1}

Cause:
Action:
FTPBC-E006022 SEVERE FTPBC-E006022: Invalid port {0}, The valid range is 1 to 65535.

Cause:
Action:
FTPBC-E006023 SEVERE FTPBC-E006023: Invalid maxSequenceNumber - {0}. The valid range is 1 to 2147483647

Cause:
Action:
FTPBC-E006024 SEVERE FTPBC-E006024: Invalid startingSequenceNumber - {0}. The valid range is 1 to 2147483647

Cause:
Action:
FTPBC-E006025 SEVERE FTPBC-E006025: Invalid persistence type - {0}. It must be one of the: {1}, {2}, {3}

Cause:
Action:
FTPBC-E006026 SEVERE FTPBC-E006026: in {0} : Failed to decrypt password. Got exception {1}

Cause:
Action:
FTPBC-E006027 SEVERE FTPBC-E006027: Invalid socksVersion value - {0}. Valid version should be {1}, {2}, or {3} (Version {3} means unknown version)

Cause:
Action:
FTPBC-E006028 SEVERE FTPBC-E006028: Invalid connection mode - {0}. Valid mode should be {1}, or {2}

Cause:
Action:
FTPBC-E006029 SEVERE FTPBC-E006029: Invalid post command - {0}. should be {1}, {2} or {3}

Cause:
Action:
FTPBC-E006030 SEVERE FTPBC-E006030: Invalid pre command - {0}. should be {1}, {2} or {3}

Cause:
Action:
FTPBC-E006031 SEVERE FTPBC-E006031: in {0} : client class {1} has wrong type. It must be type of {2}

Cause:
Action:
FTPBC-E006032 SEVERE FTPBC-E006032: in {0} : client class {1} has wrong type. It must be type of {2}

Cause:
Action:
FTPBC-E006033 SEVERE FTPBC-E006033: in {0} : Failed to encrypt password. Got exception {1}

Cause:
Action:
FTPBC-E006034 SEVERE FTPBC-E006034: Failed to list files

Cause:
Action:
FTPBC-E006035 SEVERE FTPBC-E006035: in {0} : Failed to list files - pathName is {1}, regExp is {2}, server reply is {3}

Cause:
Action:
FTPBC-E006036 SEVERE FTPBC-E006036: in {0} : Failed to change back working directory. The directory name is {1}

Cause:
Action:
FTPBC-E006037 SEVERE FTPBC-E006037: in {0} : Failed to get filter processor (regex parser or name pattern parser) - The expression is {1}, exception={2}

Cause:
Action:
FTPBC-E006038 SEVERE FTPBC-E006038: in {0} : componentID was not provided

Cause:
Action:
FTPBC-E006039 SEVERE FTPBC-E006039: in {0} : Exception when geting DB connection, make sure database jdbc:derby://localhost:1527/sample app on APP is available and started in your netbeans environment, exception={1}

Cause:
Action:
FTPBC-E006040 SEVERE FTPBC-E006040: in {0} : Exception when creating table, exception={1}

Cause:
Action:
FTPBC-E006041 SEVERE FTPBC-E006041: in {0} : Exception when open state file {1}, e = {2}

Cause:
Action:
FTPBC-E006042 SEVERE FTPBC-E006042: in {0} : invalid state {1}, e = {2}

Cause:
Action:
FTPBC-E006043 SEVERE FTPBC-E006043: in {0} : Exception when write state file {1}, e = {2}

Cause:
Action:
FTPBC-E006044 SEVERE FTPBC-E006044: in {0} : Exception when close state file {1}, e = {2}

Cause:
Action:
FTPBC-E006045 SEVERE FTPBC-E006045: in {0} : Exception when read state file {1}, e = {2}

Cause:
Action:
FTPBC-E006046 SEVERE FTPBC-E006046: feature no longer supported

Cause:
Action:
FTPBC-E006047 SEVERE FTPBC-E006047: Invalid maxSequenceNumber - {0}, should be > startingSequenceNumber - {1}

Cause:
Action:
FTPBC-E006048 SEVERE FTPBC-E006048: in {0} : Invalid (un-supported) Directory Listing Style - {1}. Please check FtpHeuristics resource for a valid list

Cause:
Action:
FTPBC-E006049 SEVERE FTPBC-E006049: cfg file: no valid delimiters

Cause:
Action:
FTPBC-E006050 SEVERE FTPBC-E006050: cfg file: incomplete line{0}

Cause:
Action:
FTPBC-E006051 SEVERE FTPBC-E006051: Heuristics configuration file {0} not found

Cause:
Action:
FTPBC-E006052 SEVERE FTPBC-E006052: Not connected

Cause:
Action:
FTPBC-E006053 SEVERE FTPBC-E006053: Exception when sleep on retry, e={0}

Cause:
Action:
FTPBC-E006054 SEVERE FTPBC-E006054: Connection to external failed: retry count = {0} error messages = {1}

Cause:
Action:
FTPBC-E006055 SEVERE FTPBC-E006055: FTP client not available when initializing FTP interface

Cause:
Action:
FTPBC-E006056 SEVERE FTPBC-E006056: Exception when creating state manager, e={0}

Cause:
Action:
FTPBC-E006057 SEVERE FTPBC-E006057: getState(): Failed to load persistent state. The persistent file may be corrupted or the format may be changed. Got exception {0}

Cause:
Action:
FTPBC-E006058 SEVERE FTPBC-E006058: StatePersistenceBaseLocation not specified

Cause:
Action:
FTPBC-E006059 SEVERE FTPBC-E006059: createManagers(): Failed to create a state persistence adapter. Got exception {0}

Cause:
Action:
FTPBC-E006060 SEVERE FTPBC-E006060: createManagers(): Failed to create a state manager

Cause:
Action:
FTPBC-E006061 SEVERE FTPBC-E006061: NamePattern.expand(): raw string to be expanded is NULL

Cause:
Action:
FTPBC-E006064 SEVERE FTPBC-E006064: in {0} : NULL Socks found in the SOCKS chain

Cause:
Action:
FTPBC-E006065 SEVERE FTPBC-E006065: in {0} : Socks server returned malformed stream. Returned length is {1} but SOCKS 4 protocol expects length {2}

Cause:
Action:
FTPBC-E006066 SEVERE FTPBC-E006066: in {0} : Connection refused by server, return = {1}

Cause:
Action:
FTPBC-E006067 SEVERE FTPBC-E006067: in {0} : Received invalid version, return = {1}

Cause:
Action:
FTPBC-E006068 SEVERE FTPBC-E006068: in {0} : Request rejected or failed, return = {1}

Cause:
Action:
FTPBC-E006069 SEVERE FTPBC-E006069: in {0} : Request rejected because the client program and identd report different user-ids {1}

Cause:
Action:
FTPBC-E006070 SEVERE FTPBC-E006070: in {0} : Request rejected becasue SOCKS server cannot connect to identd on the client, return = {1}

Cause:
Action:
FTPBC-E006071 SEVERE FTPBC-E006071: in {0} : Request rejected or failed due to unknown reason, return = {1}

Cause:
Action:
FTPBC-E006072 SEVERE FTPBC-E006072: in {0} : connection not allowed by ruleset, return = {1}

Cause:
Action:
FTPBC-E006073 SEVERE FTPBC-E006073: in {0} : network not reachable, return = {1}

Cause:
Action:
FTPBC-E006074 SEVERE FTPBC-E006074: in {0} : host not reachable, return = {1}

Cause:
Action:
FTPBC-E006075 SEVERE FTPBC-E006075: in {0} : TTL expired, return = {1}

Cause:
Action:
FTPBC-E006076 SEVERE FTPBC-E006076: in {0} : command not supported, return = {1}

Cause:
Action:
FTPBC-E006077 SEVERE FTPBC-E006077: in {0} : address not supported, return = {1}

Cause:
Action:
FTPBC-E006078 SEVERE FTPBC-E006078: in {0} : invalid address, return = {1}

Cause:
Action:
FTPBC-E006079 SEVERE FTPBC-E006079: in {0} : invalid address type received, return = {1}

Cause:
Action:
FTPBC-E006080 SEVERE FTPBC-E006080: in {0} : invalid address type, return = {1}

Cause:
Action:
FTPBC-E006081 SEVERE FTPBC-E006081: in {0} : Failed to decrypt password, esxception = {1}

Cause:
Action:
FTPBC-E006082 SEVERE FTPBC-E006082: in {0} : Missing socks user and password

Cause:
Action:
FTPBC-E006083 SEVERE FTPBC-E006083: in {0} : Wrong version is returned from USERNAME/PASSWORD sub-negotiation {1}

Cause:
Action:
FTPBC-E006084 SEVERE FTPBC-E006084: in {0} : USERNAME/PASSWORD authentication failed, return = {1}

Cause:
Action:
FTPBC-E006085 SEVERE FTPBC-E006085: in {0} : No acceptable negotiation method

Cause:
Action:
FTPBC-E006086 SEVERE FTPBC-E006086: in {0} : Cannot handle authentication method {1}

Cause:
Action:
FTPBC-E006087 SEVERE FTPBC-E006087: in {0} : Cannot determine SOCKS server {1} version, exception v4 = {2}, exception v5 = {3}

Cause:
Action:
FTPBC-E006088 SEVERE FTPBC-E006088: in {0} : Failed to create a local file state persistence adapter, directory not specified

Cause:
Action:
FTPBC-E006089 SEVERE FTPBC-E006089: in {0} : Failed to create a local file state persistence adapter, file not specified

Cause:
Action:
FTPBC-E006090 SEVERE FTPBC-E006090: in {0} : Directory specified {1} is not of directory type

Cause:
Action:
FTPBC-E006091 SEVERE FTPBC-E006091: in {0} : Failed to create the directory(ies) in the directory {1}. Exception = {2}

Cause:
Action:
FTPBC-E006092 SEVERE FTPBC-E006092: in {0} : Failed to create all or some of the directory(ies) in the directory {1}

Cause:
Action:
FTPBC-E006093 SEVERE FTPBC-E006093: in {0} : Exception when opening or creating file {1}, exception = {2}

Cause:
Action:
FTPBC-E006094 SEVERE FTPBC-E006094: in {0} : Exception when saving file {1}, exception = {2}

Cause:
Action:
FTPBC-E006095 SEVERE FTPBC-E006095: in {0} : Exception when closing file {1}, exception = {2}

Cause:
Action:
FTPBC-E006096 SEVERE FTPBC-E006096: in {0} : Exception when opening file {1} for reading, exception = {2}

Cause:
Action:
FTPBC-E006097 SEVERE FTPBC-E006097: in {0} : Exception when reading file {1}, exception = {2}

Cause:
Action:
FTPBC-R001001 INFO FTPBC-R001001: init method is called.

Cause:
Action:
FTPBC-R001002 INFO FTPBC-R001002: Registered MBean: {0}

Cause:
Action:
FTPBC-R001003 INFO FTPBC-R001003: onInstall method is called.

Cause:
Action:
FTPBC-R001004 INFO FTPBC-R001004: Completed installation.

Cause:
Action:
FTPBC-R001005 INFO FTPBC-R001005: onUninstall method is called.

Cause:
Action:
FTPBC-R001006 INFO FTPBC-R001006: Completed uninstallation.

Cause:
Action:
FTPBC-R001007 INFO FTPBC-R001007: Unregistered MBean: {0}

Cause:
Action:
FTPBC-R001008 INFO FTPBC-R001008: Registered Status Provider MBean for {0}.

Cause:
Action:
FTPBC-R001009 INFO FTPBC-R001009: Registered runtime configuration MBean for {0}.

Cause:
Action:
FTPBC-R001010 INFO FTPBC-R001010: Shutting down FTP Binding component.

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-R001013 INFO FTPBC-R001013: Started FTP BC inbound.

Cause:
Action:
FTPBC-R001014 INFO FTPBC-R001014: Started FTP BC outbound.

Cause:
Action:
FTPBC-R001015 INFO FTPBC-R001015: Stopped FTP BC outbound.

Cause:
Action:
FTPBC-R002001 INFO FTPBC-R002001: Deploying service unit: {0} from {1}.

Cause:
Action:
FTPBC-R002002 INFO FTPBC-R002002: Initializing service unit: {0} from {1}.

Cause:
Action:
FTPBC-R002003 INFO FTPBC-R002003: Successfully initialized service unit {0}.

Cause:
Action:
FTPBC-R002004 INFO FTPBC-R002004: Starting service unit: {0}.

Cause:
Action:
FTPBC-R002005 INFO FTPBC-R002005: Successfully started FTP BC.

Cause:
Action:
FTPBC-R002006 INFO FTPBC-R002006: Stopping service unit: {0}.

Cause:
Action:
FTPBC-R002007 INFO FTPBC-R002007: Successfully stopped service unit: {0}.

Cause:
Action:
FTPBC-R002008 INFO FTPBC-R002008: Shutting down service unit: {0}.

Cause:
Action:
FTPBC-R002009 INFO FTPBC-R002009: Undeploying service unit: {0} from {1}.

Cause:
Action:
FTPBC-R003001 INFO FTPBC-R003001: ServiceUnit init method called.

Cause:
Action:
FTPBC-R003002 INFO FTPBC-R003002: ServiceUnit start method called.

Cause:
Action:
FTPBC-R003003 INFO FTPBC-R003003: Successfully started service unit: {0}.

Cause:
Action:
FTPBC-R003004 INFO FTPBC-R003004: ServiceUnit stop method called.

Cause:
Action:
FTPBC-R003005 INFO FTPBC-R003005: Successfully stopped service unit: {0}.

Cause:
Action:
FTPBC-R003006 INFO FTPBC-R003006: ServiceUnit shutdown method called.

Cause:
Action:
FTPBC-R003007 INFO FTPBC-R003007: Successfully shutdown service unit: {0}.

Cause:
Action:
FTPBC-R003008 INFO FTPBC-R003008: Activated outbound endpoint for service name {0} and endpoint name {1}.

Cause:
Action:
FTPBC-R003009 INFO FTPBC-R003009: Deactivated outbound endpoint with service name {0} and endpoint name {1}.

Cause:
Action:
FTPBC-R003010 INFO FTPBC-R003010: Removing inbound message processor for endpoint {0}.

Cause:
Action:
FTPBC-R003011 INFO FTPBC-R003011: SU deploying...

Cause:
Action:
FTPBC-R004001 INFO FTPBC-R004001: Endpoint service name is {0} and endpoint name is {1}.

Cause:
Action:
FTPBC-R004002 INFO FTPBC-R004002: Inbound message processor is stopped.

Cause:
Action:
FTPBC-R004003 INFO FTPBC-R004003: Finished processing message with exchange id of {0}. Removing the exchange id...

Cause:
Action:
FTPBC-R004004 INFO FTPBC-R004004: Located service endpoint reference for service {0} and endpoint name {1}.

Cause:
Action:
FTPBC-R004005 INFO FTPBC-R004005: The endpoint {0} is not in RUNNING state, but in {1}. Ignoring the received message for exchange {2}...

Cause:
Action:
FTPBC-R004006 INFO FTPBC-R004006: Finished processing outbound messages.

Cause:
Action:
FTPBC-R004007 INFO FTPBC-R004007: Processing one-way inbound messages...

Cause:
Action:
FTPBC-R004008 INFO FTPBC-R004008: Stopping the Receiver Thread.

Cause:
Action:
FTPBC-R004009 INFO FTPBC-R004009: Received response for a consumer InOut exchange, and send response on as output for an invoke.

Cause:
Action:
FTPBC-R004010 INFO FTPBC-R004010: Poller thread shutdown, because its timeout expired - failed to poll the expected response within specified time: {0}.

Cause:
Action:
FTPBC-R004011 INFO FTPBC-R004011: Finished polling response for an consumer InOut exchange.

Cause:
Action:
FTPBC-W001001 WARNING FTPBC-W001001: Failed to register installer extension MBean.

Cause:
Action:
FTPBC-W001002 WARNING FTPBC-W001002: FTP port not specified, default used : {0}.

Cause:
Action:
FTPBC-W001003 WARNING FTPBC-W001003: Proxy port not specified, default used : {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-W001009 WARNING FTPBC-W001009: A JBI descriptor {0} parsing error occured ({1}). Version information for this component is not available.

Cause:
Action:
FTPBC-W001010 WARNING FTPBC-W001010: A JBI descriptor {0} I/O (read) error occured ({1}). Version information for this component is not available.

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-W003001 WARNING FTPBC-W003001: The service unit {0} does not contain any WSDL that has FTP BC related binding.

Cause:
Action:
FTPBC-W004001 WARNING FTPBC-W004001: FTP port not specified, default used : {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-W004003 WARNING FTPBC-W004003: NOT SUPPORTED: Received robust in-only message {0}.

Cause:
Action:
FTPBC-W004004 WARNING FTPBC-W004004: NOT SUPPORTED: Received out-only message {0}.

Cause:
Action:
FTPBC-W004005 WARNING FTPBC-W004005: Received invalid pattern info for message {0}.

Cause:
Action:
FTPBC-W004008 WARNING FTPBC-W004008: Failed processing request reply inbound messages.

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

Cause:
Action:
FTPBC-W004010 WARNING FTPBC-W004010: Unexpected message exchange status for one-way inbound: exchange ID {0} status {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:
FTPBC-W004014 WARNING FTPBC-W004014: Error when saving recovery log for message ID = {0}, serviceName={1}, endpointName={2}.

Cause:
Action:
FTPBC-W004015 WARNING FTPBC-W004015: Inbound processor interrupted while acquiring throttling, will proceed without increment throttle number, endpointName={0}.

Cause:
Action:
FTPBC-W004016 WARNING FTPBC-W004016: Message Exchange ID is NULL when saving malformed message information, newly generated UUID {0} used as error log entry name.

Cause:
Action:
FTPBC-W006001 WARNING FTPBC-W006001: in {0}: attempting to {1} file to itself, operation ignored

Cause:
Action:
FTPBC-W006002 WARNING FTPBC-W006002: in {0}: working file {1},{2} does not exist

Cause:
Action:
FTPBC-W006003 WARNING FTPBC-W006003: Some connection-related parameters (e.g. HostName, ServerPort, SOCKS settings, etc.) are changed after connection. The new changes will not take effect until next connecting time

Cause:
Action:
FTPBC-W006004 WARNING FTPBC-W006004: in {0} : Warning - The deleted file cannot be recovered

Cause:
Action:
FTPBC-W006005 WARNING FTPBC-W006005: in {0} : No qualified file is available for retrieving

Cause:
Action:
FTPBC-W006006 WARNING FTPBC-W006006: A new provider instance is created and used. If you are doing this after ftp connection, you may lose the connection and you may need to connect again

Cause:
Action:
FTPBC-W006007 WARNING FTPBC-W006007: Null working dorectory, use emptry string instead

Cause:
Action:
FTPBC-W006008 WARNING FTPBC-W006008: in {0} : Failed to list files - The directory specified does not exist. The directory name is {1}

Cause:
Action:
FTPBC-W006009 WARNING FTPBC-W006009: FtpFileValidator.validate(): Warning - for inbound transfer, you set PostTransferCommand to {0}. The same file might be retrieved repeatedly, make sure this is your intention

Cause:
Action:
FTPBC-W006010 WARNING FTPBC-W006010: FtpFileValidator.validate(): Warning - you set preTransferCommand to {0}, set output mode to Append. The transfer will be resolved same as Overwrite mode, make sure this is your intention

Cause:
Action:
FTPBC-W006011 WARNING FTPBC-W006011: FtpFileValidator.validate(): Warning - you set preTransferCommand to {0} instead of Copy, set output mode to Append. In case of some failures during transfer, the original Target File might be deleted and non-recoverable. Please make sure this behavior is your intention. To be able to recover from some failures for outbound 'Append' transfer, you should use preTransferCommand 'Copy', but it would slow system performance (especially if the Target File is large in size)

Cause:
Action:
FTPBC-W006012 WARNING FTPBC-W006012: FtpFileValidator.validate(): Warning - you set {0} to {1}. Pattern '%f' only can be used for 'PostTransferName' or 'PreTransferName', it will be replaced by empty string or be ignored.

Cause:
Action:
FTPBC-W006013 WARNING FTPBC-W006013: FtpFileValidator.validate(): Warning - you set {0} to {1}, set {2} to {3}. Your name will not be expanded. If you are expecting a name expansion, you should choose option 'Pattern'

Cause:
Action:
FTPBC-W006014 WARNING FTPBC-W006014: in {0} : Invalid parameters dirName is {1}, baseFileName is {2}

Cause:
Action:
FTPBC-W006015 WARNING FTPBC-W006015: in {0} : Invalid header regular expression - {1}, exception = {2}

Cause:
Action:
FTPBC-W006016 WARNING FTPBC-W006016: in {0} : Invalid trailer regular expression - {1}, exception = {2}

Cause:
Action:
FTPBC-W006017 WARNING FTPBC-W006017: in {0} : no SOCKS server is specified. Regular java.net.Socket will be created

Cause:
Action:
FTPBC-W006018 WARNING FTPBC-W006018: in {0} : unsupported encoding {0}, JVM default encoding used

Cause:
Action:
FTPBC-W006019 WARNING FTPBC-W006019: in {0} : no socks server specified

Cause:
Action:
FTPBC-W009001 WARNING FTPBC-W009001: There are no endpoints to create. None are listed in the jbi.xml for the {0} service unit {1}.

Cause:
Action:



Previous Next


Return to the GlassFish Documentation Home Page

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