Index Changes
View Info

Logging Codes Generated by Components

Please find the logging codes for an OpenESB component by clicking on the corresponding tab below:

Scheduler BC Logging Codes

Alert Code Severity Source Alert Detail
SCHEDBC-4001 CONFIG org.glassfish.openesb.schedulerbc.SchedulerConfiguration Set Component Configuration {0}: {1}
SCHEDBC-4002 CONFIG org.glassfish.openesb.schedulerbc.SchedulerConfiguration Set Application Configuration {0}: {1}
SCHEDBC-4003 CONFIG org.glassfish.openesb.schedulerbc.SchedulerConfiguration Set Application Variable {0}: {1}
SCHEDBC-4004 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Using Application Configuration {0} for endpoint {1}
SCHEDBC-4005 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler Group via WSDL Configuration: {0}
SCHEDBC-4006 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler Date Format via WSDL Configuration: {0}
SCHEDBC-4007 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler Mode via WSDL Configuration: {0}
SCHEDBC-4008 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler Start date via WSDL Configuration: {0}
SCHEDBC-4009 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler End date via WSDL Configuration: {0}
SCHEDBC-4010 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler Time Zone via WSDL Configuration: {0}
SCHEDBC-4011 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler Start date overridden by Application Configuration: {0}
SCHEDBC-4012 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler End date overridden by Application Configuration: {0}
SCHEDBC-4013 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler Time Zone overridden by Application Configuration: {0}
SCHEDBC-4014 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduler trigger {0}.{1} not enabled and thus bypassed
SCHEDBC-4015 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Quartz Scheduler job name {0} will be scheduled
SCHEDBC-4016 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Quartz Scheduler job descripton: {0}
SCHEDBC-4017 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduling {0} trigger {1}.{2} to fire {3} times, every {4} milliseconds
SCHEDBC-4018 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduling {0} trigger {1}.{2} to fire for condition: {3}
SCHEDBC-4019 CONFIG org.glassfish.openesb.schedulerbc.SchedulerConfiguration Obfuscated Password Application Variable {0}
SCHEDBC-4020 CONFIG org.glassfish.openesb.schedulerbc.SchedulerComponentManager Created Quartz Scheduler {0} with {1} worker threads
SCHEDBC-4021 CONFIG org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Scheduling {0} trigger {1}.{2} to fire for condition: {3} to last {4} millisecs, repeating {5} times at {6} millisecs interval
SCHEDBC-5001 INFO org.glassfish.openesb.schedulerbc.SchedulerComponentManager Start Scheduler consumer endpoints...
SCHEDBC-5002 INFO org.glassfish.openesb.schedulerbc.SchedulerComponentManager Stopped Scheduler consumer endpoints
SCHEDBC-5003 INFO org.glassfish.openesb.schedulerbc.SchedulerComponentManager Shut down Scheduler consumer endpoints...
SCHEDBC-5004 INFO org.glassfish.openesb.schedulerbc.SchedulerEndpointManager Creating endpoint for {0}
SCHEDBC-5005 INFO org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Quartz Scheduler has been started
SCHEDBC-5006 INFO org.glassfish.openesb.schedulerbc.SchedulerServiceUnitManager Quartz Scheduler has been shut down
SCHEDBC-5007 INFO org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Quartz Scheduler has been suspended
SCHEDBC-5008 INFO org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint {0} trigger {1}.{2} will fire first at: {3}
SCHEDBC-6001 WARNING org.glassfish.openesb.schedulerbc.SchedulerBootstrap SchedulerBootstrap installation MBean failed to initialize: {0}
SCHEDBC-6002 WARNING org.glassfish.openesb.schedulerbc.SchedulerComponentManager Cannot remove Quartz Scheduler for Service Assembly {0}
SCHEDBC-6003 WARNING org.glassfish.openesb.schedulerbc.SchedulerServiceUnitManager Cannot shutdown Quartz Scheduler
SCHEDBC-6004 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Cannot start Quartz Scheduler
SCHEDBC-6005 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Cannot suspend Quartz Scheduler
SCHEDBC-6006 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob Consumer endpoint {0} cannot send to (consume) provider endpoint
SCHEDBC-6007 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Cannot find Scheduler consumer endpoint {0} from Component context
SCHEDBC-6008 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.AppVarTemplate Application variable {0} is undefined
SCHEDBC-6009 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.TriggerDetails Invalid timezone ID ({0}) specified; using default instead
SCHEDBC-6010 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerStatistics Got SchedulerException in {0}:
SCHEDBC-6011 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Interuppted, so abort waiting for Message Exchange ACK/NACK
SCHEDBC-6012 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob Failed {0} attempt(s) to consume provider endpoint, disposing this trigger message instance "{1}"
SCHEDBC-6013 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob Failed {0} attempt(s) to consume provider endpoint, flagging this trigger message instance "{1}" as FAILED in Quartz
SCHEDBC-6014 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob Failed {0} attempt(s) to consume provider endpoint with this trigger message "{1}"; SUSPEND is NOT however supported by this component
SCHEDBC-6015 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob Failed to consume provider endpoint with this trigger message "{0}"
SCHEDBC-6016 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint.SchedulerJob Failed {0} attempt(s) to consume intended provider with this trigger message "{1}"; redirected to {2}-{3}
SCHEDBC-6017 WARNING org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Interrupted, so abort waiting in throttling queue
SCHEDBC-7001 SEVERE org.glassfish.openesb.schedulerbc.SchedulerComponentManager Cannot create Quartz Scheduler for Service Assembly {0}
SCHEDBC-7002 SEVERE org.glassfish.openesb.schedulerbc.SchedulerComponentManager.SchedulerJobFactory Cannot find respective Scheduler endpoint
SCHEDBC-7003 SEVERE org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint WSDL for Endpoint {0} does not represent a valid Scheduler binding
SCHEDBC-7004 SEVERE org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Cannot initialize Scheduler for endpoint {0}

FTP BC Logging Messages

Message CodeSeveritySourceMessage Detail
FTPBC-W001013 WARNING com.sun.jbi.ftpbc.InboundReceiver
 Can not find inbound message processor associated with key={0}.
FTPBC-C001999 CONFIG com.sun.jbi.ftpbc.RuntimeConfiguration
 FTPBC-C001999: Attribute changed
FTPBC-E001001 SEVERE com.sun.jbi.ftpbc.bootstrap.FTPBindingBootstrap
 FTPBC-E001001: Failed to unregister MBean: {0}
FTPBC-E001002 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddress
 FTPBC-E001002: Missing required ftp:transfer 'userDefDirListStyle' and / or 'userDefDirListHeuristics' attribute(value) for ftp operation {0} while 'useUserDefinedHeuristics' is 'true'.
FTPBC-E001003 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddress
 FTPBC-E001003: Invalid FTP Command Channel timeout {0}, should be integer >= 0, operation {1}.
FTPBC-E001004 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddress
 FTPBC-E001004: Invalid FTP Data Channel timeout {0}, should be integer >= 0, operation {1}.
FTPBC-E001005 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddressURL
 FTPBC-E001005: Missing FTP URL in ftp binding address
FTPBC-E001006 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddressURL
 FTPBC-E001006: FTP url is still a ftp url placeholder, please specify a concrete FTP address.
FTPBC-E001007 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddressURL
 FTPBC-E001007: Invalid FTP url, not starting with ftp://, url= {0}
FTPBC-E001008 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddressURL
 FTPBC-E001008: Invalid FTP url, path not allowed for a url as FTP endpoint, url= {0}
FTPBC-E001009 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddressURL
 FTPBC-E001009: Malformed FTP url, url= {0}
FTPBC-E001010 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddressURL
com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001010: Invalid port in URL, must be a positive number following host name as in localhost:21, url= {0}
FTPBC-E001011 SEVERE com.sun.jbi.ftpbc.packaging.WSDLConfigurations
 FTPBC-E001011: Failed to parse XSD file: {0} in the service assembly.
FTPBC-E001011 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddressURL
 FTPBC-E001011: Invalid FTP url, host required, url= {0}
FTPBC-E001012 SEVERE com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-E001012: Failed to start the end point with service name {0} and endpoint name {1}: {2}
FTPBC-E001012 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddressURL
 FTPBC-E001012: Invalid FTP port : {0}.
FTPBC-E001013 SEVERE com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-E001013: Failed to start the end point with service name {0} and endpoint name {1}: {2}
FTPBC-E001013 SEVERE com.sun.jbi.ftpbc.extensions.FTPExtSerializer
 FTPBC-E001013: {0} is an invalid token name.
FTPBC-E001014 SEVERE com.sun.jbi.ftpbc.extensions.FTPExtSerializer
 FTPBC-E001014: Attribute value {0} contains an empty migration application variable reference, attribute name = {1}.
FTPBC-E001014 SEVERE com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-E001014: Failed to start inbound message processor for endpoint: {0}.
FTPBC-E001015 SEVERE com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-E001015: Failed deploying SU, ID={0} error={1}
FTPBC-E001015 SEVERE com.sun.jbi.ftpbc.extensions.FTPExtSerializer
 FTPBC-E001015: application variable reference {0} in attribute value {1} (attribute name = {2}) has no definition in MBean configuration parameter "EnvironmentVariables".
FTPBC-E001016 SEVERE com.sun.jbi.ftpbc.extensions.FTPExtSerializer
 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}.
FTPBC-E001017 SEVERE com.sun.jbi.ftpbc.extensions.FTPExtSerializer
 FTPBC-E001017: Error : attribute still has un-resolved application variable reference, attribute value {0}, attribute name = {1}
FTPBC-E001018 SEVERE com.sun.jbi.ftpbc.extensions.FTPMessage
 FTPBC-E001018: Mandatory messageRepository not specified.
FTPBC-E001019 SEVERE com.sun.jbi.ftpbc.extensions.FTPMessage
 FTPBC-E001019: Missing required ftp:transfer 'encodingStyle' attribute(value) for ftp operation {0} while 'use' is 'encoded'.
FTPBC-E001020 SEVERE com.sun.jbi.ftpbc.extensions.FTPMessage
 FTPBC-E001020: Invalid message name prefix {0}, should not contain name pattern escape char '%', operation {1}.
FTPBC-E001021 SEVERE com.sun.jbi.ftpbc.extensions.FTPTransfer
 FTPBC-E001021: Both sendTo and receiveFrom for ftp:transfer not specified.
FTPBC-E001022 SEVERE com.sun.jbi.ftpbc.extensions.FTPTransfer
 FTPBC-E001022: Missing required ftp:transfer 'encodingStyle' attribute(value) for ftp operation {0} while 'use' is 'encoded'.
FTPBC-E001023 SEVERE com.sun.jbi.ftpbc.extensions.FTPTransfer
 FTPBC-E001023: Attribute {0} requires a path pointing to a file instead of path={1}.
FTPBC-E001024 SEVERE com.sun.jbi.ftpbc.extensions.FTPTransfer
 FTPBC-E001024: Pre/Post operation RENAME or COPY configured with no corresponding destination specified.
FTPBC-E001025 SEVERE com.sun.jbi.ftpbc.extensions.FTPTransfer
 FTPBC-E001025: Invalid polling interval for inbound {0}, should be integer > 0.
FTPBC-E001026 SEVERE com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001026: Missing proxy URL in ftp binding address
FTPBC-E001027 SEVERE com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001027: Proxy url is still a placeholder, please specify a concrete proxy address.
FTPBC-E001028 SEVERE com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001028: Malformed proxy url, url=
FTPBC-E001029 SEVERE com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001029: Invalid proxy url, path not allowed for a proxy url
FTPBC-E001030 SEVERE com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001030: Invalid proxy url, host required, url= {0}
FTPBC-E001031 SEVERE com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001031: No proxy host specified when 'useProxy' is set to 'true'.
FTPBC-E001032 SEVERE com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001032: Invalid Proxy port : {0}.
FTPBC-E001033 SEVERE com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001033: Invalid proxy protocol {0}, valid proxy protocols are socks4, socks5.
FTPBC-E001034 SEVERE com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-E001034: Missing proxy protocol scheme in proxy URL : {0}.
FTPBC-E001035 SEVERE com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-E001035: Component Context is null.
FTPBC-E001036 SEVERE com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-E001036: Cannot get Delivery Channel from context: {0}
FTPBC-E001037 SEVERE com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-E001037: Failed to start the outbound receiver: {0}
FTPBC-E001038 SEVERE com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-E001038: Failed to start the inbound receiver: {0}
FTPBC-E001039 SEVERE com.sun.jbi.ftpbc.RuntimeConfiguration
 FTPBC-E001039: Invalid argument for setting attribute {0}: {1}
FTPBC-E001040 SEVERE com.sun.jbi.ftpbc.RuntimeConfiguration
 FTPBC-E001040: A value of {0} is not valid for attribute {1}. The valid range is {2} - {3}.
FTPBC-E001047 SEVERE com.sun.jbi.ftpbc.RuntimeConfiguration
 FTPBC-E001047: property name is NULL when setting configuration parameters.
FTPBC-E001048 SEVERE com.sun.jbi.ftpbc.RuntimeConfiguration
 FTPBC-E001048: property value is NULL when setting configuration parameters, name={0}.
FTPBC-E001049 SEVERE com.sun.jbi.ftpbc.management.FTPBCManagement
 FTPBC-E001049: Invalid endpoint name: {0}.
FTPBC-E001050 SEVERE com.sun.jbi.ftpbc.management.FTPBCManagement
 FTPBC-E001050: Failed to suspend endpoint: {0}.
FTPBC-E001051 SEVERE com.sun.jbi.ftpbc.management.FTPBCManagement
 FTPBC-E001051: Failed to resume endpoint: {0}.
FTPBC-E001052 SEVERE com.sun.jbi.ftpbc.extensions.FTPAddress
 FTPBC-E001052: When SecuredFTP is : {0}, keystore information is required, validation failed for {1}.
FTPBC-E002001 SEVERE com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-E002001: Failed to deploy service unit due to: {0}
FTPBC-E002002 SEVERE com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-E002002: Failed to initialize service unit {0} due to: {1}
FTPBC-E002003 SEVERE com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-E002003: Error starting service unit {0} due to: {1}
FTPBC-E002004 SEVERE com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-E002004: Error stopping service unit {0} due to: {1}
FTPBC-E002005 SEVERE com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-E002005: Error shutting down service unit {0} due to: {1}
FTPBC-E002006 SEVERE com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-E002006: Service unit {0} failed pre-processing (inbound endpoint locks registration), an exception was raised. {1}
FTPBC-E002007 SEVERE com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-E002007: Exception caught when de-register EPs from inbound EP lock registry, e={0}
FTPBC-E002008 SEVERE com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-E002008: Service unit {0} failed post-processing after stop (deregister inbound endpoint locks, etc.), an exception was raised. {1}
FTPBC-E002009 SEVERE com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-E002009: Service unit {0} failed post-processing after shutdown (deregister inbound endpoint locks, etc.), an exception was raised. {1}
FTPBC-E003001 SEVERE com.sun.jbi.ftpbc.packaging.WSDLConfigurations
 FTPBC-E003001: Missing ftp:address in wsdl for this service {0}.
FTPBC-E003002 SEVERE com.sun.jbi.ftpbc.packaging.WSDLConfigurations
 FTPBC-E003002: Missing ftp:operation definition(s) in wsdl for this service {0}.
FTPBC-E003003 SEVERE com.sun.jbi.ftpbc.packaging.WSDLConfigurations
 FTPBC-E003003: Missing required Input properties for ftp binding operation {0}.
FTPBC-E003004 SEVERE com.sun.jbi.ftpbc.packaging.WSDLConfigurations
 FTPBC-E003004: Missing required / for ftp binding operation {0}.
FTPBC-E003005 SEVERE com.sun.jbi.ftpbc.packaging.WSDLConfigurations
 FTPBC-E003005: Missing required 'encodingStyle' (in /) for ftp binding operation {0} while 'use' is 'encoded'.
FTPBC-E003006 SEVERE com.sun.jbi.ftpbc.packaging.WSDLConfigurations
 FTPBC-E003006: Missing required Output properties for ftp binding operation {0}.
FTPBC-E004001 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004001: Invalid FTP port : {0}.
FTPBC-E004002 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004002: No proxy host specified when 'useProxy' is set to 'true'.
FTPBC-E004003 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004003: Invalid proxy protocol {0}, valid proxy protocols are socks4, socks5.
FTPBC-E004004 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004004: Missing FTP target file, operation = {0}.
FTPBC-E004005 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004005: Invalid ftp target spec, should be in the form of path/filename, spec={0}, operation={1}
FTPBC-E004006 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004006: No PreSendLocation specified when PreSendCommand is {0}.
FTPBC-E004007 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004007: No directory name found in PreSendLocation {0}, when PreSendCommand is RENAME or COPY.
FTPBC-E004008 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004008: No file name found in PreSendLocation {0} when PostSendCommand is RENAME or COPY.
FTPBC-E004009 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004009: No PostSendLocation specified when PostSendCommand is {0}.
FTPBC-E004010 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004010: No directory name found in PostSendLocation {0} when PostSendCommand is RENAME or DELETE.
FTPBC-E004011 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004011: No file name found in PostSendLocation {0} when PostSendCommand is RENAME or DELETE.
FTPBC-E004012 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004012: Missing messageRepository - a path pointing to a remote directory where message transfer occurs.
FTPBC-E004013 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004013: Message tag instance {0} not starting with UUID, messageName={1}, operation={2}.
FTPBC-E004014 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004014: Invalid UUID instance {0}, length < 36, messageName={1}, operaiton={2}.
FTPBC-E004015 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004015: Attribute messageName {0} does not start with %u, while UUID instance {1} is provided to substitute UUID symbol, operation = {2}.
FTPBC-E004016 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004016: Invalid extensibility element : {0}
FTPBC-E004017 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004017: No UUID available when a consumer is polling response with message correlate enabled.
FTPBC-E004018 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004018: No PreReceiveLocation specified when PreReceiveCommand is {0}.
FTPBC-E004019 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004019: No directory name found in PreReceiveLocation {0}, when PreReceiveCommand is RENAME or COPY.
FTPBC-E004020 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004020: No file name found in PreReceiveLocation {0} when PostSendCommand is RENAME or COPY.
FTPBC-E004021 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004021: No PostReceiveLocation specified when PostReceiveCommand is {0}.
FTPBC-E004022 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004022: No directory name found in PostReceiveLocation {0} when PostReceiveCommand is RENAME or DELETE.
FTPBC-E004023 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004023: No file name found in PostReceiveLocation {0} when PostReceiveCommand is RENAME or DELETE.
FTPBC-E004024 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004024: Missing stage directory, operation {0}.
FTPBC-E004025 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004025: Missing stage file, operation {0}.
FTPBC-E004026 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004026: Exception when preparing ftp connection parameters for FTP get or poll, servicename={0}, endpoint={1}, e={2}.
FTPBC-E004029 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004029: Failed to locate the service endpoint reference for service {0} and endpoint name {1}.
FTPBC-E004030 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004030: Failed to send message: {0}
FTPBC-E004031 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004031: Encountered an invalid inbound message: null.
FTPBC-E004032 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004032: Encountered an invalid message exchange pattern of {0} while processing the message exchange reply status.
FTPBC-E004033 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004033: Inbound message exchange error: status is not DONE, status={0}, message exchange ID={1}
FTPBC-E004034 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004034: Encountered an invalid message exchange id of {0} while processing the message exchange reply status.
FTPBC-E004035 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004035: Invalid message exchange pattern for ftp operation {0}.
FTPBC-E004036 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004036: Missing required Input properties for inbound ftp operation {0}.
FTPBC-E004037 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004037: Missing required / properties for inbound ftp operation {0}.
FTPBC-E004038 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004038: Invalid child element found for , expecting / for inbound ftp operation {0}.
FTPBC-E004039 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004039: Missing required Output properties for request-response type inbound ftp operation {0}.
FTPBC-E004040 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004040: Invalid child element found for , expecting / for inbound ftp operation {0}.
FTPBC-E004041 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004041: Unable to resolve endpoint reference for service name {0} and endpoint name {1}.
FTPBC-E004042 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004042: Unexpected exception: {0}
FTPBC-E004043 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004043: Missing required Output properties for inbound ftp operation {0}.
FTPBC-E004044 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004044: Missing required ftp:transfer element for inbound ftp operation {0}.
FTPBC-E004045 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004045: Missing required Input properties for outbound ftp operation {0}.
FTPBC-E004046 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004046: Missing required ftp:transfer element for outbound ftp operation {0}.
FTPBC-E004048 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004048: Missing required Output properties for polling response for ftp operation {0}.
FTPBC-E004049 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004049: Missing required extensibility element / element for polling response for ftp operation {0}.
FTPBC-E004051 SEVERE com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004051: Unexpected exception: {0}
FTPBC-E004052 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004052: Failed to allocate connection, key = {0}: {1}
FTPBC-E004053 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004053: MBeanException caught when try to suspend endpoint (redelivery): serviceName={0}, endpointName={1}, error message={2}.
FTPBC-E004054 SEVERE com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-E004054: %p representing current target directory should not appear in Pre/Post operation's target file name pattern : {0}
FTPBC-E004060 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004060: Failed to write message: ServiceUnit ID : {0}, address : {1}, destination : {2}, exception : {3}
FTPBC-E004061 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004061: Exception when send error during error handling: exception = {0}.
FTPBC-E004062 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004062: FTPBC Runtime validation error: service unit : {0}, address : {1}, target info : {2}, error : {3}
FTPBC-E004063 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004063: FTP connection error: connection key: {0}, exception : {1}
FTPBC-E004065 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004065: Error retrieving FTP target file: connection key : {0}, target file : {1}, exception : {2}
FTPBC-E004066 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004066: Error when instatiating and starting response poller in synchronized request response processing \n
FTPBC-E004067 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004067: Exception when create fault during error handling: exception = {0}.
FTPBC-E004068 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004068: Exception when applying NM properties to endpoint binding: service unit : {0}, address : {1}, target info : {2}, error : {3}
FTPBC-E004069 SEVERE com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004069: Exception when normalizing response message: service unit : {0}, address : {1}, target info : {2}, error : {3}
FTPBC-E004070 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004070: Exception when instantiate response poller: service unit : {0}, address : {1}, target info : {2}, error : {3}
FTPBC-E004071 SEVERE com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004071: Exception when schedule response poller timeout : service unit : {0}, address : {1}, target info : {2}, response poller timeout : {3}, error : {3}
FTPBC-E004072 SEVERE com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004072: Exception when configuring response poller : service unit : {0}, address : {1}, target info : {2}, error : {3}
FTPBC-E004073 SEVERE com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004073: Exception when getting connection from pool : service unit : {0}, address : {1}, target info : {2}, connection key : {3}, error : {4}
FTPBC-E004074 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004074: {0}::FtpInterface not available, FTP configuration: key = {1}
FTPBC-E004075 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004075: {0}::FtpFileClient not available, FTP configuration: key = {1}
FTPBC-E004076 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004076: {0}::FtpFileProvider not available, FTP configuration: key = {1}
FTPBC-E004077 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004077: Inbound processor aborted, Error validating inbound message exchange properties - {0}
FTPBC-E004078 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004078: Thread {0} interrupted when acquiring semaphore: {1}
FTPBC-E004079 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004079: Exception when connect, connection key={0}, exception={1}
FTPBC-E004080 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004080: Exception returning connection: key={0}, exception={1}
FTPBC-E004081 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004081: can not resolve destination for pre transfer operation {0}, thread {1}, PreDirectoryName = {2}, PreDirectoryNameIsPattern = {3}, PreFileName = {4}, PreFileNameIsPattern = {5}.
FTPBC-E004082 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004082: Error when completing pending FTP command at the end of retrieving remote file, return code = {0}, return text = {1}.
FTPBC-E004083 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004083: Failed to mkdir: dir = {0}, FTP return code = {1}, return text = {2}.
FTPBC-E004084 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004084: {0}::FtpFileConfiguration not available, FTP configuration: key = {1}
FTPBC-E004085 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-E004085: Failed to put file: dir = {0}, file = {1}, FTP return code = {2}, return text = {3}.
FTPBC-E004086 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
 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}.
FTPBC-E004087 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004087: Malformed recovery log entry: expected prefix = {0} line={1}
FTPBC-E004088 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004088: Error parsing recovery log entry: path = {0} exception = {1}
FTPBC-E004089 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004089: Exception processing recovery log entry: messageID = {0} log-path = {1} exception = {2}
FTPBC-E004090 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004090: Exception when saving info regarding a malformed message or payload during {0}: message exchange ID = {1} exception = {2}
FTPBC-E004091 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004091: in {0}: calling {1} failed, return text = {2}
FTPBC-E004092 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004092: Exception {0} in {1}
FTPBC-E004093 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 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}
FTPBC-E004094 SEVERE com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004094: Exception when sending message into NMR: service unit : {0}, address : {1}, target info : {2}, error : {3}
FTPBC-E004095 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004095: in {0}: calling {1} failed, return text = {2}
FTPBC-E005001 SEVERE com.sun.jbi.ftpbc.FTPDenormalizer
 FTPBC-E005001: Encountered an invalid binding operation name '{0}' for FTP BC.
FTPBC-E005002 SEVERE com.sun.jbi.ftpbc.FTPDenormalizer
 FTPBC-E005002: Encountered invalid message exchange pattern for FTP BC operation '{0}'.
FTPBC-E005003 SEVERE com.sun.jbi.ftpbc.FTPDenormalizer
 FTPBC-E005003: Encountered invalid message type definition for FTP BC operation '{0}'.
FTPBC-E005004 SEVERE com.sun.jbi.ftpbc.FTPDenormalizer
 FTPBC-E005004: Can not find the encoder while processing encoded data - denormalization : message part = {0}, use = {1}, encodingStyle = {2}.
FTPBC-E005005 SEVERE com.sun.jbi.ftpbc.FTPNormalizer
 FTPBC-E005005: Exception when creating wrapper builder in FTPNormalizer, e={0}
FTPBC-E005006 SEVERE com.sun.jbi.ftpbc.FTPNormalizer
 FTPBC-E005006: Exception when creating doc builder in FTPNormalizer, e={0}
FTPBC-E005007 SEVERE com.sun.jbi.ftpbc.FTPNormalizer
 FTPBC-E005007: Exception when creating transformer in FTPNormalizer, e={0}
FTPBC-E005008 SEVERE com.sun.jbi.ftpbc.FTPNormalizer
 FTPBC-E005008: Encountered invalid message type definition for FTP BC operation '{0}'.
FTPBC-E005010 SEVERE com.sun.jbi.ftpbc.FTPNormalizer
 FTPBC-E005010: Can not find the encoder while processing encoded data - normalization : message part = {0}, use = {1}, encodingStyle = {2}.
FTPBC-E005011 SEVERE com.sun.jbi.ftpbc.FTPNormalizer
 FTPBC-E005011: Error occured while transforming the normalized message: {0}
FTPBC-E006001 SEVERE com.sun.jbi.ftpbc.ftp.FtpDirRegExp
com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
com.sun.jbi.ftpbc.ftp.FtpFileProviderImpl
com.sun.jbi.ftpbc.ftp.FtpFileStateDBPersistenceAdapter
com.sun.jbi.ftpbc.ftp.FtpFileTransferNamesAndCommands
com.sun.jbi.ftpbc.ftp.FtpFileTransferNamesAndCommandsGet
com.sun.jbi.ftpbc.ftp.FtpFileTransferNamesAndCommandsPut
com.sun.jbi.ftpbc.ftp.FtpHeuristics
com.sun.jbi.ftpbc.ftp.FtpInterface
com.sun.jbi.ftpbc.ftp.Socks
com.sun.jbi.ftpbc.ftp.SocksChain
com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006001: Exception {0} in {1}
FTPBC-E006002 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006002: doRawCommands(): ftp raw command {0} failed - reason text = {1};
FTPBC-E006003 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006003: doRawCommands(): ftp raw command {0} failed - exception = {1};
FTPBC-E006004 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006004: configureSocks(): Invalid configuration parameters - No SOCKS
FTPBC-E006005 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006005: open(): provider.connect() failed - return text = {0}
FTPBC-E006006 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006006: open(): provider.login() failed - return text = {0}
FTPBC-E006007 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
com.sun.jbi.ftpbc.ftp.FtpFileProviderImpl
 FTPBC-E006007: in {0}: calling {1} failed, return text = {2}
FTPBC-E006008 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006008: in {0}: Invalid command {1} used
FTPBC-E006009 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006009: in {0} : Failed to create destination directory {1}
FTPBC-E006010 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006010: in {0} : output stream already exists
FTPBC-E006011 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006011: in {0} : Failed to create working directory {1}
FTPBC-E006012 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006012: in {0} : input stream already exists
FTPBC-E006013 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006013: No connection is available. The ConnectionEstablishmentMode is {0}
FTPBC-E006014 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006014: No connection is available. connection mode is {0}, the connection may have timed out, call connect()
FTPBC-E006015 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006015: in {0} : Exception when saving persistent state, e={1}
FTPBC-E006016 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-E006016: in {0} : Exception when resolving target file.
FTPBC-E006017 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006017: in {0} : Missing directory listing style
FTPBC-E006018 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006018: Failed to update heuristics using directory listing style {0}. Got exception {1}
FTPBC-E006019 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
com.sun.jbi.ftpbc.ftp.FtpFileProviderImpl
 FTPBC-E006019: Missing user defined heuristics configuration file when setting user defined directory listing style {0}
FTPBC-E006020 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006020: in {0} : Failed to update heuristics using user defined directory listing style {1}. Got exception {2}
FTPBC-E006021 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
com.sun.jbi.ftpbc.ftp.FtpFileValidator
com.sun.jbi.ftpbc.ftp.FtpHeuristics
 FTPBC-E006021: Missing or invalid parameter {0}, value {1}
FTPBC-E006022 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006022: Invalid port {0}, The valid range is 1 to 65535.
FTPBC-E006023 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006023: Invalid maxSequenceNumber - {0}. The valid range is 1 to 2147483647
FTPBC-E006024 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006024: Invalid startingSequenceNumber - {0}. The valid range is 1 to 2147483647
FTPBC-E006025 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006025: Invalid persistence type - {0}. It must be one of the: {1}, {2}, {3}
FTPBC-E006026 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006026: in {0} : Failed to decrypt password. Got exception {1}
FTPBC-E006027 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
com.sun.jbi.ftpbc.ftp.Socks
com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006027: Invalid socksVersion value - {0}. Valid version should be {1}, {2}, or {3} (Version {3} means unknown version)
FTPBC-E006028 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006028: Invalid connection mode - {0}. Valid mode should be {1}, or {2}
FTPBC-E006029 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006029: Invalid post command - {0}. should be {1}, {2} or {3}
FTPBC-E006030 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006030: Invalid pre command - {0}. should be {1}, {2} or {3}
FTPBC-E006031 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006031: in {0} : client class {1} has wrong type. It must be type of {2}
FTPBC-E006032 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006032: in {0} : client class {1} has wrong type. It must be type of {2}
FTPBC-E006033 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 FTPBC-E006033: in {0} : Failed to encrypt password. Got exception {1}
FTPBC-E006034 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileProviderImpl
 FTPBC-E006034: Failed to list files
FTPBC-E006035 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileProviderImpl
 FTPBC-E006035: in {0} : Failed to list files - pathName is {1}, regExp is {2}, server reply is {3}
FTPBC-E006036 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileProviderImpl
 FTPBC-E006036: in {0} : Failed to change back working directory. The directory name is {1}
FTPBC-E006037 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileProviderImpl
 FTPBC-E006037: in {0} : Failed to get filter processor (regex parser or name pattern parser) - The expression is {1}, exception={2}
FTPBC-E006038 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileStateDBPersistenceAdapter
 FTPBC-E006038: in {0} : componentID was not provided
FTPBC-E006039 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileStateDBPersistenceAdapter
 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}
FTPBC-E006040 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileStateDBPersistenceAdapter
 FTPBC-E006040: in {0} : Exception when creating table, exception={1}
FTPBC-E006041 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileStatePersistenceAdapter
 FTPBC-E006041: in {0} : Exception when open state file {1}, e = {2}
FTPBC-E006042 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileStatePersistenceAdapter
 FTPBC-E006042: in {0} : invalid state {1}, e = {2}
FTPBC-E006043 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileStatePersistenceAdapter
 FTPBC-E006043: in {0} : Exception when write state file {1}, e = {2}
FTPBC-E006044 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileStatePersistenceAdapter
 FTPBC-E006044: in {0} : Exception when close state file {1}, e = {2}
FTPBC-E006045 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileStatePersistenceAdapter
 FTPBC-E006045: in {0} : Exception when read state file {1}, e = {2}
FTPBC-E006046 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileValidator
 FTPBC-E006046: feature no longer supported
FTPBC-E006047 SEVERE com.sun.jbi.ftpbc.ftp.FtpFileValidator
 FTPBC-E006047: Invalid maxSequenceNumber - {0}, should be > startingSequenceNumber - {1}
FTPBC-E006048 SEVERE com.sun.jbi.ftpbc.ftp.FtpHeuristics
 FTPBC-E006048: in {0} : Invalid (un-supported) Directory Listing Style - {1}. Please check FtpHeuristics resource for a valid list
FTPBC-E006049 SEVERE com.sun.jbi.ftpbc.ftp.FtpHeuristicsProperties
 FTPBC-E006049: cfg file: no valid delimiters
FTPBC-E006050 SEVERE com.sun.jbi.ftpbc.ftp.FtpHeuristicsProperties
 FTPBC-E006050: cfg file: incomplete line{0}
FTPBC-E006051 SEVERE com.sun.jbi.ftpbc.ftp.FtpHeuristicsProperties
 FTPBC-E006051: Heuristics configuration file {0} not found
FTPBC-E006052 SEVERE com.sun.jbi.ftpbc.ftp.FtpInterface
 FTPBC-E006052: Not connected
FTPBC-E006053 SEVERE com.sun.jbi.ftpbc.ftp.FtpInterface
 FTPBC-E006053: Exception when sleep on retry, e={0}
FTPBC-E006054 SEVERE com.sun.jbi.ftpbc.ftp.FtpInterface
 FTPBC-E006054: Connection to external failed: retry count = {0} error messages = {1}
FTPBC-E006055 SEVERE com.sun.jbi.ftpbc.ftp.FtpInterface
 FTPBC-E006055: FTP client not available when initializing FTP interface
FTPBC-E006056 SEVERE com.sun.jbi.ftpbc.ftp.FtpInterface
 FTPBC-E006056: Exception when creating state manager, e={0}
FTPBC-E006057 SEVERE com.sun.jbi.ftpbc.ftp.FtpInterface
 FTPBC-E006057: getState(): Failed to load persistent state. The persistent file may be corrupted or the format may be changed. Got exception {0}
FTPBC-E006058 SEVERE com.sun.jbi.ftpbc.ftp.FtpInterface
 FTPBC-E006058: StatePersistenceBaseLocation not specified
FTPBC-E006059 SEVERE com.sun.jbi.ftpbc.ftp.FtpInterface
 FTPBC-E006059: createManagers(): Failed to create a state persistence adapter. Got exception {0}
FTPBC-E006060 SEVERE com.sun.jbi.ftpbc.ftp.FtpInterface
 FTPBC-E006060: createManagers(): Failed to create a state manager
FTPBC-E006061 SEVERE com.sun.jbi.ftpbc.ftp.namepattern.NamePattern
 FTPBC-E006061: NamePattern.expand(): raw string to be expanded is NULL
FTPBC-E006064 SEVERE com.sun.jbi.ftpbc.ftp.SocksChain
 FTPBC-E006064: in {0} : NULL Socks found in the SOCKS chain
FTPBC-E006065 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006065: in {0} : Socks server returned malformed stream. Returned length is {1} but SOCKS 4 protocol expects length {2}
FTPBC-E006066 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006066: in {0} : Connection refused by server, return = {1}
FTPBC-E006067 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006067: in {0} : Received invalid version, return = {1}
FTPBC-E006068 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006068: in {0} : Request rejected or failed, return = {1}
FTPBC-E006069 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006069: in {0} : Request rejected because the client program and identd report different user-ids {1}
FTPBC-E006070 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006070: in {0} : Request rejected becasue SOCKS server cannot connect to identd on the client, return = {1}
FTPBC-E006071 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006071: in {0} : Request rejected or failed due to unknown reason, return = {1}
FTPBC-E006072 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006072: in {0} : connection not allowed by ruleset, return = {1}
FTPBC-E006073 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006073: in {0} : network not reachable, return = {1}
FTPBC-E006074 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006074: in {0} : host not reachable, return = {1}
FTPBC-E006075 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006075: in {0} : TTL expired, return = {1}
FTPBC-E006076 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006076: in {0} : command not supported, return = {1}
FTPBC-E006077 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006077: in {0} : address not supported, return = {1}
FTPBC-E006078 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006078: in {0} : invalid address, return = {1}
FTPBC-E006079 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006079: in {0} : invalid address type received, return = {1}
FTPBC-E006080 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006080: in {0} : invalid address type, return = {1}
FTPBC-E006081 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006081: in {0} : Failed to decrypt password, esxception = {1}
FTPBC-E006082 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006082: in {0} : Missing socks user and password
FTPBC-E006083 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006083: in {0} : Wrong version is returned from USERNAME/PASSWORD sub-negotiation {1}
FTPBC-E006084 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006084: in {0} : USERNAME/PASSWORD authentication failed, return = {1}
FTPBC-E006085 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006085: in {0} : No acceptable negotiation method
FTPBC-E006086 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006086: in {0} : Cannot handle authentication method {1}
FTPBC-E006087 SEVERE com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-E006087: in {0} : Cannot determine SOCKS server {1} version, exception v4 = {2}, exception v5 = {3}
FTPBC-E006088 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006088: in {0} : Failed to create a local file state persistence adapter, directory not specified
FTPBC-E006089 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006089: in {0} : Failed to create a local file state persistence adapter, file not specified
FTPBC-E006090 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006090: in {0} : Directory specified {1} is not of directory type
FTPBC-E006091 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006091: in {0} : Failed to create the directory(ies) in the directory {1}. Exception = {2}
FTPBC-E006092 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006092: in {0} : Failed to create all or some of the directory(ies) in the directory {1}
FTPBC-E006093 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006093: in {0} : Exception when opening or creating file {1}, exception = {2}
FTPBC-E006094 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006094: in {0} : Exception when saving file {1}, exception = {2}
FTPBC-E006095 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006095: in {0} : Exception when closing file {1}, exception = {2}
FTPBC-E006096 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006096: in {0} : Exception when opening file {1} for reading, exception = {2}
FTPBC-E006097 SEVERE com.sun.jbi.ftpbc.ftp.statemanager.FileStatePersistenceAdapter
 FTPBC-E006097: in {0} : Exception when reading file {1}, exception = {2}
FTPBC-R001001 INFO com.sun.jbi.ftpbc.bootstrap.FTPBindingBootstrap
 FTPBC-R001001: init method is called.
FTPBC-R001002 INFO com.sun.jbi.ftpbc.bootstrap.FTPBindingBootstrap
 FTPBC-R001002: Registered MBean: {0}
FTPBC-R001003 INFO com.sun.jbi.ftpbc.bootstrap.FTPBindingBootstrap
 FTPBC-R001003: onInstall method is called.
FTPBC-R001004 INFO com.sun.jbi.ftpbc.bootstrap.FTPBindingBootstrap
 FTPBC-R001004: Completed installation.
FTPBC-R001005 INFO com.sun.jbi.ftpbc.bootstrap.FTPBindingBootstrap
 FTPBC-R001005: onUninstall method is called.
FTPBC-R001006 INFO com.sun.jbi.ftpbc.bootstrap.FTPBindingBootstrap
 FTPBC-R001006: Completed uninstallation.
FTPBC-R001007 INFO com.sun.jbi.ftpbc.bootstrap.FTPBindingBootstrap
 FTPBC-R001007: Unregistered MBean: {0}
FTPBC-R001008 INFO com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-R001008: Registered Status Provider MBean for {0}.
FTPBC-R001009 INFO com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-R001009: Registered runtime configuration MBean for {0}.
FTPBC-R001010 INFO com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-R001010: Shutting down FTP Binding component.
FTPBC-R001011 INFO com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-R001011: FTP Binding component {0} shutdown completed.
FTPBC-R001012 INFO com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-R001012: FTP Binding component stopped {0}.
FTPBC-R001013 INFO com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-R001013: Started FTP BC inbound.
FTPBC-R001014 INFO com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-R001014: Started FTP BC outbound.
FTPBC-R001015 INFO com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-R001015: Stopped FTP BC outbound.
FTPBC-R002001 INFO com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-R002001: Deploying service unit: {0} from {1}.
FTPBC-R002002 INFO com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-R002002: Initializing service unit: {0} from {1}.
FTPBC-R002003 INFO com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-R002003: Successfully initialized service unit {0}.
FTPBC-R002004 INFO com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-R002004: Starting service unit: {0}.
FTPBC-R002005 INFO com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-R002005: Successfully started FTP BC.
FTPBC-R002006 INFO com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-R002006: Stopping service unit: {0}.
FTPBC-R002007 INFO com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-R002007: Successfully stopped service unit: {0}.
FTPBC-R002008 INFO com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-R002008: Shutting down service unit: {0}.
FTPBC-R002009 INFO com.sun.jbi.ftpbc.FTPBindingDeployer
 FTPBC-R002009: Undeploying service unit: {0} from {1}.
FTPBC-R003001 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003001: ServiceUnit init method called.
FTPBC-R003002 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003002: ServiceUnit start method called.
FTPBC-R003003 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003003: Successfully started service unit: {0}.
FTPBC-R003004 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003004: ServiceUnit stop method called.
FTPBC-R003005 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003005: Successfully stopped service unit: {0}.
FTPBC-R003006 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003006: ServiceUnit shutdown method called.
FTPBC-R003007 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003007: Successfully shutdown service unit: {0}.
FTPBC-R003008 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003008: Activated outbound endpoint for service name {0} and endpoint name {1}.
FTPBC-R003009 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003009: Deactivated outbound endpoint with service name {0} and endpoint name {1}.
FTPBC-R003010 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003010: Removing inbound message processor for endpoint {0}.
FTPBC-R003011 INFO com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-R003011: SU deploying...
FTPBC-R004001 INFO com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-R004001: Endpoint service name is {0} and endpoint name is {1}.
FTPBC-R004002 INFO com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-R004002: Inbound message processor is stopped.
FTPBC-R004003 INFO com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-R004003: Finished processing message with exchange id of {0}. Removing the exchange id...
FTPBC-R004004 INFO com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-R004004: Located service endpoint reference for service {0} and endpoint name {1}.
FTPBC-R004005 INFO com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-R004005: The endpoint {0} is not in RUNNING state, but in {1}. Ignoring the received message for exchange {2}...
FTPBC-R004006 INFO com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-R004006: Finished processing outbound messages.
FTPBC-R004007 INFO com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-R004007: Processing one-way inbound messages...
FTPBC-R004008 INFO com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-R004008: Stopping the Receiver Thread.
FTPBC-R004009 INFO com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-R004009: Received response for a consumer InOut exchange, and send response on as output for an invoke.
FTPBC-R004010 INFO com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-R004010: Poller thread shutdown, because its timeout expired - failed to poll the expected response within specified time: {0}.
FTPBC-R004011 INFO com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-R004011: Finished polling response for an consumer InOut exchange.
FTPBC-W001001 WARNING com.sun.jbi.ftpbc.bootstrap.FTPBindingBootstrap
 FTPBC-W001001: Failed to register installer extension MBean.
FTPBC-W001002 WARNING com.sun.jbi.ftpbc.extensions.FTPAddressURL
 FTPBC-W001002: FTP port not specified, default used : {0}.
FTPBC-W001003 WARNING com.sun.jbi.ftpbc.extensions.ProxyAddressURL
 FTPBC-W001003: Proxy port not specified, default used : {0}.
FTPBC-W001004 WARNING com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-W001004: Failed to register status provider MBean.
FTPBC-W001005 WARNING com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-W001005: Failed to register configuration MBean.
FTPBC-W001006 WARNING com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-W001006: Failed to un-register status provider MBean for {0}
FTPBC-W001007 WARNING com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-W001007: Failed to un-register runtime configuration MBean for {0}
FTPBC-W001008 WARNING com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-W001008: Failed to stop the outbound receiver:
FTPBC-W001009 WARNING com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-W001009: A JBI descriptor {0} parsing error occured ({1}). Version information for this component is not available.
FTPBC-W001010 WARNING com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-W001010: A JBI descriptor {0} I/O (read) error occured ({1}). Version information for this component is not available.
FTPBC-W001011 WARNING com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-W001011: Exception when register status mbean, e={0}
FTPBC-W001012 WARNING com.sun.jbi.ftpbc.FTPBindingLifeCycle
 FTPBC-W001012: Exception when register FTPBC management mbean, e={0}
FTPBC-W003001 WARNING com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-W003001: The service unit {0} does not contain any WSDL that has FTP BC related binding.
FTPBC-W004001 WARNING com.sun.jbi.ftpbc.FtpClientParameterGenerator
 FTPBC-W004001: FTP port not specified, default used : {0}.
FTPBC-W004002 WARNING com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-W004002: When messageCorrelate is 'true', inbound message processing expects a matched file name as: {0}, but got {1}.
FTPBC-W004003 WARNING com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-W004003: NOT SUPPORTED: Received robust in-only message {0}.
FTPBC-W004004 WARNING com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-W004004: NOT SUPPORTED: Received out-only message {0}.
FTPBC-W004005 WARNING com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-W004005: Received invalid pattern info for message {0}.
FTPBC-W004008 WARNING com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-W004008: Failed processing request reply inbound messages.
FTPBC-W004009 WARNING com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-W004009: Failed processing one-way outbound messages, exception : {0}.
FTPBC-W004010 WARNING com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-W004010: Unexpected message exchange status for one-way inbound: exchange ID {0} status {1}.
FTPBC-W004011 WARNING com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-W004011: Failed processing one-way inbound messages, exception: {0}.
FTPBC-W004012 WARNING com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-W004012: About to suspend endpoint: serviceName={0}, endpointName={1}.
FTPBC-W004013 WARNING com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-W004013: Can not locate recovery log for message ID = {0}, path= {1}, serviceName={2}, endpointName={3}.
FTPBC-W004014 WARNING com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-W004014: Error when saving recovery log for message ID = {0}, serviceName={1}, endpointName={2}.
FTPBC-W004015 WARNING com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-W004015: Inbound processor interrupted while acquiring throttling, will proceed without increment throttle number, endpointName={0}.
FTPBC-W004016 WARNING com.sun.jbi.ftpbc.OutboundMessageProcessor
 FTPBC-W004016: Message Exchange ID is NULL when saving malformed message information, newly generated UUID {0} used as error log entry name.
FTPBC-W006001 WARNING com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-W006001: in {0}: attempting to {1} file to itself, operation ignored
FTPBC-W006002 WARNING com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-W006002: in {0}: working file {1},{2} does not exist
FTPBC-W006003 WARNING com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 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
FTPBC-W006004 WARNING com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-W006004: in {0} : Warning - The deleted file cannot be recovered
FTPBC-W006005 WARNING com.sun.jbi.ftpbc.ftp.FtpFileClientImpl
 FTPBC-W006005: in {0} : No qualified file is available for retrieving
FTPBC-W006006 WARNING com.sun.jbi.ftpbc.ftp.FtpFileConfiguration
 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
FTPBC-W006007 WARNING com.sun.jbi.ftpbc.ftp.FtpFileProviderImpl
 FTPBC-W006007: Null working dorectory, use emptry string instead
FTPBC-W006008 WARNING com.sun.jbi.ftpbc.ftp.FtpFileProviderImpl
 FTPBC-W006008: in {0} : Failed to list files - The directory specified does not exist. The directory name is {1}
FTPBC-W006009 WARNING com.sun.jbi.ftpbc.ftp.FtpFileValidator
 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
FTPBC-W006010 WARNING com.sun.jbi.ftpbc.ftp.FtpFileValidator
 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
FTPBC-W006011 WARNING com.sun.jbi.ftpbc.ftp.FtpFileValidator
 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)
FTPBC-W006012 WARNING com.sun.jbi.ftpbc.ftp.FtpFileValidator
 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.
FTPBC-W006013 WARNING com.sun.jbi.ftpbc.ftp.FtpFileValidator
 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'
FTPBC-W006014 WARNING com.sun.jbi.ftpbc.ftp.FtpHeuristics
 FTPBC-W006014: in {0} : Invalid parameters dirName is {1}, baseFileName is {2}
FTPBC-W006015 WARNING com.sun.jbi.ftpbc.ftp.FtpHeuristics
 FTPBC-W006015: in {0} : Invalid header regular expression - {1}, exception = {2}
FTPBC-W006016 WARNING com.sun.jbi.ftpbc.ftp.FtpHeuristics
 FTPBC-W006016: in {0} : Invalid trailer regular expression - {1}, exception = {2}
FTPBC-W006017 WARNING com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-W006017: in {0} : no SOCKS server is specified. Regular java.net.Socket will be created
FTPBC-W006018 WARNING com.sun.jbi.ftpbc.ftp.SocksSocket
 FTPBC-W006018: in {0} : unsupported encoding {0}, JVM default encoding used
FTPBC-W006019 WARNING com.sun.jbi.ftpbc.ftp.SocksSocket
com.sun.jbi.ftpbc.ftp.SocksSocketFactory
 FTPBC-W006019: in {0} : no socks server specified
FTPBC-W009001 WARNING com.sun.jbi.ftpbc.ServiceUnitImpl
 FTPBC-W009001: There are no endpoints to create. None are listed in the jbi.xml for the {0} service unit {1}.

XsltSE Logging Codes

Alert Code Severity Source Alert Detail
XSLTSE-4003 Config com.sun.jbi.engine.xslt.XsltSEExchangeHandler Starting XsltSE with transformation engine\: {0}
XSLTSE-5001 Info com.sun.jbi.engine.xslt.XsltseComponentManager Initialized XSLT service engine successfully\!
XSLTSE-5002 Info com.sun.jbi.engine.xslt.XsltseComponentManager Started XSLT service engine successfully\!
XSLTSE-5003 Info com.sun.jbi.engine.xslt.XsltseComponentManager Stopped XSLT service engine successfully\!
XSLTSE-5004 Info com.sun.jbi.engine.xslt.XsltseComponentManager Shut down XSLT service engine successfully\!
XSLTSE-6003 Warning com.sun.jbi.engine.xslt.XSLTSEBootstrap XsltSEBootstrap installation MBean failed to initialize\: {0}

Common Util Logging Codes

Alert Code Severity Source Alert Detail
UTIL-4001 Config com.sun.jbi.common.util.AbstractPool Resizing pool\: new size\={0}
UTIL-6001 Warning com.sun.jbi.common.descriptor.ServiceAssemblyDescriptor
com.sun.jbi.common.descriptor.parsers.ServiceAssemblyParser 		Failed to parse service assembly descriptor\: {0}
UTIL-6002 Warning com.sun.jbi.common.descriptor.ServicesDescriptor
com.sun.jbi.common.descriptor.parsers.ServicesParser 		Failed to parse service unit descriptor\: {0}
UTIL-6003 Warning com.sun.jbi.common.descriptor.parsers.ConnectionParser Failed to parse service assembly connections\: {0}
UTIL-6004 Warning com.sun.jbi.common.descriptor.ServicesDescriptor
com.sun.jbi.common.xml.XmlUtil 		Descriptor file does not exist\: {0}
UTIL-6005 Warning com.sun.jbi.common.descriptor.parsers.ServiceAssemblyParser Failed to parse Identification element\: {0}
UTIL-6006 Warning com.sun.jbi.common.util.NDC Invalid context, may not be NULL or zero length\!
UTIL-6007 Warning com.sun.jbi.common.util.NDC Invalid context, must be in key-value pairs\!
UTIL-6008 Warning com.sun.jbi.common.xml.XmlResourceImpl XmlResource failed to create DocumentBuilder\: {0}
UTIL-6009 Warning com.sun.jbi.common.xml.XmlResourceImpl XmlResource failed to create Transformer\: {0}
UTIL-6010 Warning com.sun.jbi.common.xml.XmlUtil Failed to convert to DOMSource\: {0}
UTIL-6011 Warning com.sun.jbi.common.xml.XmlUtil Failed to reset StreamSource\: {0}
UTIL-6012 Warning com.sun.jbi.common.util.MBeanHelper Unable to register MBean, forced unregister failed for\: {0}
UTIL-6013 Warning com.sun.jbi.common.util.MBeanHelper Failed to register MBean {0}\: {1}
UTIL-6014 Warning com.sun.jbi.common.util.MBeanHelper Failed to unregister MBean {0}\: {1}

QoS Logging Codes

Alert Code Severity Source Alert Detail
QOS-4001 Config com.sun.jbi.common.qos.config.RuntimeConfiguration Successfully added new Application Configuration\: {0}
QOS-4002 Config com.sun.jbi.common.qos.config.RuntimeConfiguration Successfully added new Application Variable\: {0} - Value \= {1}
QOS-4003 Config com.sun.jbi.common.qos.config.RuntimeConfiguration Successfully deleted Application Configuration\: {0}
QOS-4004 Config com.sun.jbi.common.qos.config.RuntimeConfiguration Successfully deleted Application Variable\: {0}
QOS-4005 Config com.sun.jbi.common.qos.config.RuntimeConfiguration Successfully set Application Configuration\: {0}
QOS-4006 Config com.sun.jbi.common.qos.config.RuntimeConfiguration Successfully set Application Variable\: {0} - Value \= {1}
QOS-6001 Warning com.sun.jbi.common.qos.messaging.filter.RedeliveryFilter Redelivery to error endpoint aborted, endpoint not active.
QOS-6002 Warning com.sun.jbi.common.qos.messaging.filter.RedeliveryFilter Redelivery to error endpoint aborted, no configured endpoint.
QOS-6003 Warning com.sun.jbi.common.qos.descriptor.QosAssemblyDescriptor Failed to parse QoS configuration\: {0}
QOS-6004 Warning com.sun.jbi.common.qos.descriptor.QosServicesDescriptor Descriptor file does not exist\: {0}
QOS-6005 Warning com.sun.jbi.common.qos.config.ComponentConfig
com.sun.jbi.common.qos.config.ConfigParser 		Failed to parse component configuration\: {0}
QOS-6006 Warning com.sun.jbi.common.qos.messaging.filter.RedeliveryFilter Failed to activate redelivery endpoint\: {0}
QOS-6007 Warning com.sun.jbi.common.qos.messaging.filter.RedeliveryFilter Unsupported failure option {0} for exchange\: {1}
QOS-6008 Warning com.sun.jbi.common.qos.messaging.filter.RedeliveryFilter Redelivery attempts exhausted, suspend message\: {0}
QOS-6009 Warning com.sun.jbi.common.qos.messaging.filter.RedeliveryFilter Redelivery attempts exhausted, delete message\: {0}
QOS-6010 Warning com.sun.jbi.common.qos.messaging.filter.AbstractExchangeFilter Invalid redelivery configuration\: {0} not supported for {1}\!
QOS-6011 Warning com.sun.jbi.common.qos.config.ComponentConfig {0} does not support Application Variables\!
QOS-6012 Warning com.sun.jbi.common.qos.config.ComponentConfig Component's JBI descriptor not found\:
QOS-6013 Warning com.sun.jbi.common.qos.messaging.ExchangeUtil Failed to set error data - 'error' and 'actor' cannot be empty\!
QOS-6014 Warning com.sun.jbi.common.qos.descriptor.parsers.TrackingParser Failed to parse systemic message tracking configuration\: {0}
QOS-6015 Warning com.sun.jbi.common.qos.messaging.ExchangeUtil Exchange({0}) terminated. Please review logs for details.
QOS-6016 Warning com.sun.jbi.common.qos.config.ConfigPersistence Failed to load configuration {0}\: {1}
QOS-6017 Warning com.sun.jbi.common.qos.config.ConfigPersistence Failed to persist configuration settings to file {0}\: {1}
QOS-6018 Warning com.sun.jbi.common.qos.descriptor.DeploymentLookup Provider endpoint cannot be NULL\!
QOS-6019 Warning com.sun.jbi.common.qos.messaging.filter.RedeliveryFilter Redelivery attempts exhausted, send aborted for message exchange\: {0}
QOS-6020 Warning com.sun.jbi.common.qos.messaging.filter.RedeliveryFilter.SendTask Attempting redelivery for {0}, send failed\: {1}
QOS-6021 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Invalid Application Variable Item Size\: {0}
QOS-6022 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Invalid Application Variable - Missing Name Field\: {0}
QOS-6023 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Invalid Application Variable - Missing Value Field\: {0}
QOS-6024 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Invalid Application Variable - Missing Type Field\: {0}
QOS-6025 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Application Configuration is missing field\: {0}
QOS-6026 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Application Configuration is missing value for field\: {0}
QOS-6027 Warning com.sun.jbi.common.qos.config.AbstractConfigMBean Failed to persist {0} application configuration\: {1}
QOS-6028 Warning com.sun.jbi.common.qos.config.AbstractConfigMBean Failed to persist {0} component configuration\: {1}
QOS-6029 Warning com.sun.jbi.common.qos.config.ConfigPersistence Component Configuration file {0} does not exist\!
QOS-6030 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Add Application Configuration Failed\: Configuration {0} already exists\!
QOS-6031 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Add Application Configuration Failed\: Configuration should have {0} fields, not {1}\!
QOS-6032 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Add Application Configuration Failed\: Configuration missing {0} key\!
QOS-6033 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Add Application Configuration Failed\: {0} value is invalid\!
QOS-6034 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Add Application Variable Failed\: Variable {0} already exists\!
QOS-6035 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Add Application Variable Failed\: {0} value is invalid\!
QOS-6036 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Delete Application Configuration Failed\: Configuration {0} does not exist\!
QOS-6037 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Application Variable Delete Failed\: Variable {0} does not exist\!
QOS-6038 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Set Application Configuration Failed\: Configuration {0} does not exist\!
QOS-6039 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Set Application Configuration Failed\: Configuration should have {0} fields, not {1}\!
QOS-6040 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Set Application Configuration Failed\: Configuration missing {0} key\!
QOS-6041 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Set Application Configuration Failed\: {0} value is invalid\!
QOS-6042 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Set Application Variable Failed\: Variable {0} does not exist\!
QOS-6043 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Set Application Variable Failed\: {0} value is invalid\!
QOS-6044 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Application Configuration {0} - Value Invalid\: {1}
QOS-6045 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Failed to convert NULL Property type\!
QOS-6046 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Component Configuration does not support the type\: {0}
QOS-6047 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Failed to initialize Application Configuration\: {0}
QOS-6048 Warning com.sun.jbi.common.qos.config.RuntimeConfiguration Failed to initialize Application Variables\: {0}
QOS-6049 Warning com.sun.jbi.common.qos.descriptor.DeploymentLookup Failed to create DeploymentServiceMBean for {0}\: {1}
QOS-6050 Warning com.sun.jbi.common.qos.descriptor.DeploymentLookup Failed to lookup {0} Service Qualities\: {1}
QOS-6051 Warning com.sun.jbi.common.qos.descriptor.DeploymentLookup Failed to acquire Consumers for {0} Provider {1}\: {2}
QOS-6052 Warning com.sun.jbi.common.qos.descriptor.DeploymentLookup Failed to acquire Service Assembly for Service Unit {0}\: {1}
QOS-6053 Warning com.sun.jbi.common.qos.config.ConfigPersistence Component Application Configuration file {0} does not exist\!
QOS-6054 Warning com.sun.jbi.common.qos.config.ConfigPersistence Failed to load application configuration {0}\: {1}
QOS-6055 Warning com.sun.jbi.common.qos.config.ConfigPersistence Failed to persist application configuration settings to file {0}\: {1}
QOS-6056 Warning com.sun.jbi.common.qos.messaging.filter.RedeliveryFilter Message Exchange {0} has been sent unsuccessfully {1} times; resetting redelivery counter.
QOS-6057 Warning com.sun.jbi.common.qos.config.ComponentConfig {0} does not support Application Configurations\!
QOS-6058 Warning com.sun.jbi.common.qos.descriptor.DeploymentLookup Failed to acquire DeploymentService when fetching ServiceAssembly for service unit\: {0}
QOS-6059 Warning com.sun.jbi.common.qos.descriptor.DeploymentLookup Failed to acquire DeploymentService when fetching consumers for provider\: {0}
QOS-6060 Warning com.sun.jbi.common.qos.descriptor.DeploymentLookup Failed to acquire DeploymentService when fetching service qualities\!
QOS-6061 Warning com.sun.jbi.common.qos.descriptor.parsers.RedeliveryParser Failed to parse systemic redelivery configuration\: {0}
QOS-6062 Warning com.sun.jbi.common.qos.descriptor.parsers.ThrottlingParser Failed to parse systemic throttling configuration\: {0}
QOS-6063 Warning com.sun.jbi.common.qos.messaging.BaseMessagingChannel Failed to install service qualities for service unit "{0}"\: {1}

Component Toolkit Logging Codes

Alert Code Severity Source Alert Detail
COMPTK-5001 Info com.sun.jbi.component.toolkit.lifecycle.impl.AbstractComponentManager Initialized {0} successfully\!
COMPTK-5002 Info com.sun.jbi.component.toolkit.lifecycle.impl.AbstractComponentManager Started {0} successfully\!
COMPTK-5003 Info com.sun.jbi.component.toolkit.lifecycle.impl.AbstractComponentManager Stopped {0} successfully\!
COMPTK-5004 Info com.sun.jbi.component.toolkit.lifecycle.impl.AbstractComponentManager Shut down {0} successfully\!
COMPTK-5005 Info com.sun.jbi.component.toolkit.endpoint.impl.DefaultEndpointLifeCycle {0} created NULL endpoint (info\={1}) for service unit\: {2}
COMPTK-5006 Info com.sun.jbi.component.toolkit.lifecycle.impl.AcceptPoller Failed to acquire delivery channel - may be closed\!
COMPTK-6001 Warning com.sun.jbi.component.toolkit.lifecycle.AbstractBootstrap Failed to parse component descriptor\: {0}
COMPTK-6002 Warning com.sun.jbi.component.toolkit.lifecycle.AbstractBootstrap Failed to initialize component bootstrap\: {0}
COMPTK-6003 Warning com.sun.jbi.component.toolkit.lifecycle.AbstractBootstrap Failed to register component bootstrap\: {0}
COMPTK-6004 Warning com.sun.jbi.component.toolkit.endpoint.impl.DefaultEndpointLifeCycle Service unit "{0}" failed to start consumer endpoints\: {1}
COMPTK-6005 Warning com.sun.jbi.component.toolkit.endpoint.impl.DefaultEndpointLifeCycle Duplicate endpoint ({0}) in component\: {1}
COMPTK-6006 Warning com.sun.jbi.component.toolkit.endpoint.impl.DefaultEndpointLifeCycle Duplicate endpoint ({0}) in service unit\: {1}
COMPTK-6007 Warning com.sun.jbi.component.toolkit.endpoint.impl.DefaultEndpointLifeCycle Service unit "{0}" failed to start provider endpoints\: {1}
COMPTK-6008 Warning com.sun.jbi.component.toolkit.endpoint.impl.DefaultEndpointLifeCycle Failed to deactivate endpoint\: {0}
COMPTK-6009 Warning com.sun.jbi.component.toolkit.endpoint.impl.DefaultEndpointLifeCycle Endpoint "{0}" deactivation failed\: {1}
COMPTK-6010 Warning com.sun.jbi.component.toolkit.endpoint.impl.DefaultEndpointLifeCycle Service unit "{0}" failed to stop provisioning endpoints\: {1}
COMPTK-6011 Warning com.sun.jbi.component.toolkit.endpoint.impl.DefaultEndpointLifeCycle Service unit "{0}" failed to stop consumer endpoints\: {1}
COMPTK-6012 Warning com.sun.jbi.component.toolkit.lifecycle.impl.AbstractComponentManager {0} failed to close DeliveryChannel\: {0}
COMPTK-6013 Warning com.sun.jbi.component.toolkit.lifecycle.impl.AbstractExchangeHandler Failed to start "{0}" NMR pollers\: {1}
COMPTK-6014 Warning com.sun.jbi.component.toolkit.lifecycle.impl.AbstractExchangeHandler Failed to stop "{0}" NMR poller\: {1}
COMPTK-6015 Warning com.sun.jbi.component.toolkit.lifecycle.impl.AcceptPoller An exception interrupted "{1}" NMR poller\: {0}
COMPTK-6016 Warning com.sun.jbi.component.toolkit.lifecycle.impl.AcceptPoller "{0}" NMR poller encountered error\: {1}
COMPTK-6017 Warning com.sun.jbi.component.toolkit.lifecycle.impl.DefaultServiceUnitManager Service unit already deployed\: {0}
COMPTK-6018 Warning com.sun.jbi.component.toolkit.lifecycle.impl.DefaultServiceUnitManager Failed to deploy SU "{0}"\: {1}
COMPTK-6019 Warning com.sun.jbi.component.toolkit.lifecycle.impl.DefaultServiceUnitManager shutDown failed for undeployed service unit "{0}"
COMPTK-6020 Warning com.sun.jbi.component.toolkit.lifecycle.impl.DefaultServiceUnitManager start failed for undeployed service unit "{0}"
COMPTK-6021 Warning com.sun.jbi.component.toolkit.lifecycle.impl.DefaultServiceUnitManager Service unit "{0}" start failed\: {1}
COMPTK-6022 Warning com.sun.jbi.component.toolkit.lifecycle.impl.DefaultServiceUnitManager stop failed for undeployed service unit "{0}"
COMPTK-6023 Warning com.sun.jbi.component.toolkit.lifecycle.impl.DefaultServiceUnitManager Service unit "{0}" stop failed\: {1}
COMPTK-6024 Warning com.sun.jbi.component.toolkit.lifecycle.impl.DefaultServiceUnitManager Failed to undeploy service unit "{0}"\: {1}
COMPTK-6025 Warning com.sun.jbi.component.toolkit.util.alerter.impl.AlerterImpl Event Management mbean "{0}" not found ({1})\! Please verify appropriate RAR is installed and started.
COMPTK-6026 Warning com.sun.jbi.component.toolkit.util.alerter.impl.AlerterImpl Sending {0} Alert failed\: {1}
COMPTK-6027 Warning com.sun.jbi.component.toolkit.util.alerter.AlerterFactory Invalid EventForwarder MBean name\: {0}
COMPTK-6028 Warning com.sun.jbi.component.toolkit.lifecycle.impl.AbstractExchangeHandler Failed to send message exchange (id\={0})\: {1}
COMPTK-6029 Warning com.sun.jbi.component.toolkit.lifecycle.impl.AbstractExchangeHandler Failed to create exchange - unsupported pattern\: {0}
COMPTK-6030 Warning com.sun.jbi.component.toolkit.lifecycle.impl.AbstractExchangeHandler {0} cannot find provisioning endpoint (name\={1},srvc\={2}) for message (id\={3})
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-15) was last changed on 24-Mar-09 11:31 AM, -0700 by EdWong