Index Changes
View Info

Alert Codes generated by Components

Please refer to DeveloperAlertNotificationGuidelines for more information.

HTTP BC

AlertCodeSeveritySourceAlert Detail
HTTPBC-S00800criticalcom.sun.jbi.httpsoapbc.OutboundReceiverFailed to process message exchange
HTTPBC-S00801criticalcom.sun.jbi.httpsoapbc.OutboundReceiverFailed to accept message exchange from the NMR. This is not a recoverable error. HTTP BC will stop accepting from NMR.
HTTPBC-E00720warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessorProvider for service Plugin insertion failed: Could not find plugin 0 endpoint Plugin insertion failed: Could not find plugin 1 responded with an error status. Error detail is: {2}
HTTPBC-E00721warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor Provider for service Plugin insertion failed: Could not find plugin 0 endpoint Plugin insertion failed: Could not find plugin 1 responded with an error status. No detail was provided.
HTTPBC-E00751warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor Message exchange {0} cannot be processed because its exchange pattern, robust in-only, is not supported
HTTPBC-W00758warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor An exception occured while processing a request message. {0}
HTTPBC-E00759warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor An exception occured while processing a reply message. {0}
HTTPBC-E00775warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor An exception occured while processing message exchange {0}
HTTPBC-E00776criticalcom.sun.jbi.httpsoapbc.OutboundMessageProcessor Failed to create SOAP normalize/denormalizer. {0}
HTTPBC-E00777warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor Failed to create HTTP normalizer. {0}
HTTPBC-E00778warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor Failed to create OutboundMessageProcessor. {0}
HTTPBC-E00779warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor An exception occured while attempting to sending a reply
HTTPBC-E00780warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor An exception occured while attempting to set the status of a message exchange
HTTPBC-E00805warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor Failed to process the 'suspend' redelivery on-failure option for endpoint with service name Plugin insertion failed: Could not find plugin 0, endpoint name Plugin insertion failed: Could not find plugin 1: {2}
HTTPBC-E00806warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor Maximum redelivery attempts has been exhausted, endpoint with service name Plugin insertion failed: Could not find plugin 0 and endpoint name Plugin insertion failed: Could not find plugin 1 will be suspended per the configured redelivery on-failure option...
HTTPBC-E01036warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor An exception occured while attempting to redeliver a message exchange with message group ID: {0}, message ID: {1}.
HTTPBC-E01050warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor Received an invalid address URL {0} value on the org.glassfish.openesb.address.url normalized message property. Will proceed with normal service invocation using the default configured address URL.
HTTPBC-E01051warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor Failed to create a javax.xml.ws.Dispatch object required to invoke a (external) service for endpoint {0} defined in WSDL {1} in composite application {2}.
HTTPBC-E01052warningcom.sun.jbi.httpsoapbc.OutboundMessageProcessor The value set on the org.glassfish.openesb.address.url normalized message property is invalid. This property is expected to be of String type only.
HTTPBC-E00151warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor Unable to find component that provisions endpoint {0}. Ensure that the service unit for the provisioning component has been deployed.
HTTPBC-E00701warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor Failed to locate the operation in the requested endpoint {0} that matches the message signature
HTTPBC-E00741criticalcom.sun.jbi.httpsoapbc.InboundMessageProcessor SOAP message validator error: {0}
HTTPBC-E00748warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor An exception occured while processing message exchange {0} for {1}
HTTPBC-E00749warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor Invalid/unsupported HTTP verb encountered: {0}
HTTPBC-E00750warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor Unsupported message type: {0}
HTTPBC-E00751warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor Message exchange {0} cannot be processed because its exchange pattern, robust in-only, is not supported
HTTPBC-E00771warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor Failed to send InOnly message
HTTPBC-E00772warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor Failed to send InOut message
HTTPBC-E00773warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor The requested endpoint {0} does not have any defined operations
HTTPBC-E00774warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor Message Exchange Pattern {0} is invalid for endpoint {1}
HTTPBC-E00805warningcom.sun.jbi.httpsoapbc.InboundMessageProcessor Failed to process the 'suspend' redelivery on-failure option for endpoint with service name Plugin insertion failed: Could not find plugin 0, endpoint name Plugin insertion failed: Could not find plugin 1: {2}
HTTPBC-E00101criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle {0} failed to start. {1}
HTTPBC-E00141criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle Cannot obtain binding channel from context. {0}
HTTPBC-E00152warningcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle Failed to parse the descriptor file for identity information; file descriptor file is {0}
HTTPBC-E00153warningcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycleFailed to read the descriptor file for identity information; descriptor file is {0}
HTTPBC-E00154warningcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle Failed to create a DocumentBuilder to parse the descriptor file for identity information; descriptor file is {0}
HTTPBC-R00101infocom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle{0} started with the following configuration:
HTTPBC-R00103infocom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle {0} shut down
HTTPBC-R00105infocom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle {0} stopped
HTTPBC-E00104criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle Failed to stop {0}. {1}
HTTPBC-W00120criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle An exception occurred while attempting to register the status provider MBean: {0}
HTTPBC-W00121criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle An exception occurred while attempting to register the extension MBean: {0}
HTTPBC-W00122criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle An exception occurred while attempting to register the runtime configuration MBean: {0}
HTTPBC-W00123criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle An exception occurred while attempting to deregister the status provider MBean: {0}
HTTPBC-W00124warningcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle An exception occurred while attempting to unregister the extension MBean: {0}
HTTPBC-W00125criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle An exception occurred while attempting to unregister the runtime configuration MBean: {0}
HTTPBC-W00126criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle An exception occurred while attempting to register the management MBean: {0}
HTTPBC-W00127criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle An exception occurred while attempting to unregister the management MBean: {0}
HTTPBC-W01303infocom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCyclesun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID Plugin insertion failed: Could not find plugin 0. The endpoint ID is either invalid or it does not represent a valid inbound (consuming) endpoint targeted for this binding. The current resume() call will be ignored...
HTTPBC-W01304criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCyclesun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID Plugin insertion failed: Could not find plugin 0. The endpoint ID is either invalid or it does not represent a valid inbound (consuming) endpoint targeted for this binding. The current suspend() call will be ignored...
HTTPBC-W01305infocom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID Plugin insertion failed: Could not find plugin 0. The endpoint ID is either invalid or it does not represent a valid inbound (consuming) endpoint targeted for this binding. The current isEndpointActive() call returns 'false' by default...
HTTPBC-W01306infocom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle resume() operation only applies to inbound(consuming) endpoints. Ignoring current resume() request because endpoint with the ID of Plugin insertion failed: Could not find plugin 0 is not a consumer endpoint.
HTTPBC-W01307infocom.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle suspend() operation only applies to inbound(consuming) endpoints. Ignoring current suspend() request because endpoint with the ID of Plugin insertion failed: Could not find plugin 0 is not a consumer endpoint.
HTTPBC-E00201criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingDeployer Deployment failed. {0}
HTTPBC-E00203criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingDeployerInitialization failed. {0}
HTTPBC-E00205criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingDeployer Start failed. {0}
HTTPBC-E00206criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingDeployer Stop failed
HTTPBC-E00210criticalcom.sun.jbi.httpsoapbc.HttpSoapBindingDeployer Shutdown failed
HTTPBC-W00671warningcom.sun.jbi.httpsoapbc.HttpSoapBindingComponentAn exception occured while attempting to resolve endpoint reference.
HTTPBC-E01028warningcom.sun.jbi.httpsoapbc.security.am.impl.AmHelper Failed to load Sun Access Manager configuration properties file {0}: {1}
HTTPBC-E01041warningcom.sun.jbi.httpsoapbc.security.am.impl.AmHelper Unable to find the Access Manager configuration properties file {0} in directory {1}

JMS BC

AlertCodeSeveritySourceAlert Detail
JMSBC-W0502warningcom.sun.jbi.jmsbc.recovery.JMSConnectionInfoFilePersister JMSBC-W0502: Failed to close the file-based connection information persister with directory {0} and filename {1}: {2}
JMSBC-W0703warningcom.sun.jbi.jmsbc.util.SynchronizedStateChange com.sun.jbi.jmsbc.JMSBindingComponent JMSBC-W0703:The assumption failed. Report this...
JMSBC-W0205warningcom.sun.jbi.jmsbc.jms.SendChannelJCAImpl JMSBC-W0205: Failed to delete temporary {0} with name {1}: {2}
JMSBC-E0757criticalcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-E0757: Failed to prepare the channel(s) for endpoint {0} of service {1}
JMSBC-E0726criticalcom.sun.jbi.jmsbc.JMSBindingDeployer JMSBC-E0726: Failed to deploy the service unit {0} from service unit path {1}: {2}
JMSBC-E0731criticalcom.sun.jbi.jmsbc.JMSNormalizer com.sun.jbi.jmsbc.JMSDenormalizer JMSBC-E0731: The JMS message property {0} is of an unknown type {1}
JMSBC-W0720warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0720:Some other thread is running the shutdown for endpoint {0}
JMSBC-W0206warningcom.sun.jbi.jmsbc.jms.SendChannelJCAImpl JMSBC-W0206: Failed to close MessageConsumer which is receiving on temporary {0} with name {1}: {2}
JMSBC-W0724warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0724:Failed to retrieve QOS from service unit root path {0}.
JMSBC-W0708warningcom.sun.jbi.jmsbc.JMSDenormalizer JMSBC-W0708: The message part {0} did not get added as a JMS MapMessage property with name {1} as type {2}; there is no such WSDL message part with the name {0}
JMSBC-W0716warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0716: Error occurred while deactivating endpoint {0} of service {1} for service unit {2}: {3}
JMSBC-W0732warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0732:Suspended endpoint {0}
JMSBC-W0730warningcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-W0730:Unable to denormalize reply from internal service engine/binding component for message exchange {0}, end point {1} and operation {2}.
JMSBC-W0709warningcom.sun.jbi.jmsbc.JMSDenormalizer JMSBC-W0709: The message part {0} did not get added as JMS TextMessage text; there is no such WSDL message part with the name {0}
JMSBC-W0501warningcom.sun.jbi.jmsbc.recovery.JMSConnectionInfoFilePersister JMSBC-W0501: Found an unexpected connection value {0} in a connection record in directory {1}, filename {2}
JMSBC-E0309criticalcom.sun.jbi.jmsbc.mbeans.RuntimeConfiguration JMSBC-E0309: Failed to load application configuration from {0} got error {1}
JMSBC-E0761criticalcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-E0761: Transaction rollback failed for transaction {0} , endpoint {1} of service {2}. The current status of transaction is {4}
JMSBC-E0714criticalcom.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint JMSBC-E0714: Failed to set the {0} property to true on the JMS message Plugin insertion failed: Could not find plugin 1: {2}
JMSBC-E0762criticalcom.sun.jbi.jmsbc.JMSBindingComponent JMSBC-E0762: Could not register management MBean for component {0}.
JMSBC-W0002warningcom.sun.jbi.jmsbc.extensions.JMSExtSerializer JMSBC-W0002: Found an unexpected attribute {0} for element {1} in service definition {2}; this attribute will be ignored
JMSBC-E0308criticalcom.sun.jbi.jmsbc.mbeans.RuntimeConfiguration JMSBC-E0308: Failed to load application variable {0} got error {1}
JMSBC-W0710warningcom.sun.jbi.jmsbc.JMSNormalizer com.sun.jbi.jmsbc.JMSDenormalizer JMSBC-W0710: The mapping of TextMessage text to WSDL message part is not defined, by using the attribute {0}, in the JMS binding operation's input/output binding
JMSBC-E0752criticalcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-E0752: Received the following error on the message exchange with ID {0} and pattern {1}: {2}
JMSBC-E0708criticalcom.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint JMSBC-E0708: Failed to commit XA transaction Plugin insertion failed: Could not find plugin 0: {1}
JMSBC-W0717warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0717: Error occurred while removing channel(s) for endpoint {0} of service {1} for service unit {2}: {3}
JMSBC-W0102warningcom.sun.jbi.jmsbc.jca.MCFManager JMSBC-W0102: Failed to find a matching ManagedConnectionFactory with connectionURL {0}, merged options {1}
JMSBC-W0728warningcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-W0728:Unable to send message to JMS provider, message exchange {0}, end point {1} and operation {2}.
JMSBC-W0504warningcom.sun.jbi.jmsbc.recovery.JMSXARecovery JMSBC-W0504: Failed to register XAResource (registerXAResource) to connection {0} for transaction recovery; will try again on next JMS BC initialization
JMSBC-W0101warningcom.sun.jbi.jmsbc.jca.RAManager JMSBC-W0101: Failed to find a matching ResourceAdapter with connectionURL {0}, merged options {1}
JMSBC-W0712warningcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-W0712: Failed to call setRollbackOnly on XA transaction Plugin insertion failed: Could not find plugin 0 for processing message exchange with ID {1} and exchange pattern {2} due to error: {3}
JMSBC-W0715warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0715: The service unit {0} does not contain any WSDL(s) for which the JMS Binding Component is responsible
JMSBC-W0704warningcom.sun.jbi.jmsbc.JMSBindingComponent JMSBC-W0704: Failed to parse the component JBI descriptor {0}; component identity information (version, build number, etc.) is not be available: {1}
JMSBC-W0204warningcom.sun.jbi.jmsbc.jms.SendChannelJCAImpl JMSBC-W0204: Timed out waiting for JMS reply message on temporary {0} with name {1} after {2} milliseconds
JMSBC-E0728criticalcom.sun.jbi.jmsbc.JMSBindingDeployer JMSBC-E0728: Failed to start the service unit {0}: {1}
JMSBC-E0743criticalcom.sun.jbi.jmsbc.OutboundMessageProcessor com.sun.jbi.jmsbc.OutboundReceiver JMSBC-E0743: An error occurred while attempting to receive a message exchange from the delivery channel or while processing a message exchange: {0}
JMSBC-E0709criticalcom.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint JMSBC-E0709: Failed to rollback XA transaction Plugin insertion failed: Could not find plugin 0: {1}
JMSBC-W0733warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0733:Resumed endpoint {0}
JMSBC-E0727criticalcom.sun.jbi.jmsbc.JMSBindingDeployer JMSBC-E0727: Failed to shut down the service unit {0}: {1}
JMSBC-W0706warningcom.sun.jbi.jmsbc.JMSDenormalizer JMSBC-W0706: The content of message part {0} is null for the WSDL message {1}
JMSBC-W0719warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0719: One or more operation(s) were marked for XA transaction for service {0}, endpoint {1}, connection {2}; but unable to persist connection information due to error, no recovery for this connection on restart: {3}
JMSBC-W0701warningcom.sun.jbi.jmsbc.OutboundMessageProcessor com.sun.jbi.jmsbc.util.SynchronizedStateChange com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint JMSBC-W0701:Lifecycle event lock is not acquired/released in right order for endpoint {0}
JMSBC-E0730criticalcom.sun.jbi.jmsbc.JMSNormalizer com.sun.jbi.jmsbc.JMSDenormalizer JMSBC-E0730: The JMS message property {0} is of an unsupported type {1}
JMSBC-E0764criticalcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-E0764: Could not suspend endpoint {0}.
JMSBC-E0749criticalcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-E0749: Failed to send the message exchange with ID {0} and pattern {1} on the delivery channel due to error: {2}
JMSBC-E0713criticalcom.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint JMSBC-E0713: Failed to process JMS message Plugin insertion failed: Could not find plugin 0 in onMessage: {1}
JMSBC-E0729criticalcom.sun.jbi.jmsbc.JMSBindingDeployer JMSBC-E0729: Failed to stop the service unit {0}: {1}
JMSBC-W0201warningcom.sun.jbi.jmsbc.jms.ReceiveChannelJCAImpl JMSBC-W0201: Timed out waiting for dispatched threads to complete after {0} seconds, connection is {1}, destination is {2}
JMSBC-I0701infocom.sun.jbi.jmsbc.JMSBindingBootstrap com.sun.jbi.jmsbc.util.JMSBCContext JMSBC-I0701: Unsupported onfailure option {0}. Only "suspend" and "error" can be applied for (IN-OUT message exchange) service {1} , endpoint {2} and operation {3}
JMSBC-E0707criticalcom.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint JMSBC-E0707: Failed to set rollback XA transaction Plugin insertion failed: Could not find plugin 0: {1}
JMSBC-E0747criticalcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-E0747: Failed to process the message exchange with ID {0} and exchange pattern {1} due to error: {2}
JMSBC-E0755criticalcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-E0755: Failed to stop endpoint {0} of service {1} for service unit {2}: {3}
JMSBC-E0318criticalcom.sun.jbi.jmsbc.mbeans.RuntimeConfiguration JMSBC-E0318: Failed to persist application configuration {0} got error {1}
JMSBC-E0721criticalcom.sun.jbi.jmsbc.JMSBindingComponent JMSBC-E0721: Failed to register status MBean for component {0}
JMSBC-W0503warningcom.sun.jbi.jmsbc.recovery.JMSXARecovery JMSBC-W0503: Recovery of transactions is not supported by the JBI runtime in which the JMS BC is running
JMSBC-W0001warningcom.sun.jbi.jmsbc.extensions.JMSExtSerializer JMSBC-W0001: Found an environment variable {0} for attribute {1} in service definition {2} but there is no value assigned for it; it will be ignored
JMSBC-W0707warningcom.sun.jbi.jmsbc.JMSDenormalizer JMSBC-W0707: No mapping is defined between the WSDL message part(s) and the the JMS MapMessage property(ies) in the JMS binding operation's input/output binding
JMSBC-W0718warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0718: Failed to open outbound channel but will proceed with SU deployment and attempt to connect later during message processing; service unit {0}, service {1}, endpoint {2}, operation {3}: {4}
JMSBC-W0727warningcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-W0727:Unable to process message exchange {0}, end point {1} and operation {2}.
JMSBC-W0203warningcom.sun.jbi.jmsbc.jms.SendChannelJCAImpl JMSBC-W0203: Failed to close connection to {0}: {1}
JMSBC-W0731warningcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-W0731:The provider is not able to process the message. The error is in the the data format. If dead letter queue is specified in the redelivery handling then the message would be copied to the dead letter queue after making specified number of attempts. The message exchange
JMSBC-E0701criticalcom.sun.jbi.jmsbc.InboundMessageProcessorFactory JMSBC-E0701: Failed to create a MessageEndpoint
JMSBC-W0705warningcom.sun.jbi.jmsbc.JMSBindingComponent JMSBC-W0705: Failed to read the component JBI descriptor {0} due to an I/O error; component identity information (version, build number, etc.) is not be available: {1}
JMSBC-W0721warningcom.sun.jbi.jmsbc.ServiceUnitImpl JMSBC-W0721:Waited long enough for in process messages to complete. Shutting down the endpoint {0}
JMSBC-E0748criticalcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-E0748: Failed to set the status on the message exchange with ID {0} and pattern {1} due to error: {2}
JMSBC-E0772criticalcom.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint JMSBC-E0772: Unable to decode the message and in jmsOperation redelivery is set to {0}. Either it is not specified or specified with no Dead-letter-queue/delete action is not specified. This message would continue to be re delivered and would never be processed.
JMSBC-E0317criticalcom.sun.jbi.jmsbc.mbeans.RuntimeConfiguration JMSBC-E0317: Failed to persist application variable {0} got error {1}
JMSBC-W0505warningcom.sun.jbi.jmsbc.recovery.JMSXARecovery JMSBC-W0505: Failed to determine whether transaction recovery is supported by the JBI runtime due to error: {0}
JMSBC-E0725criticalcom.sun.jbi.jmsbc.JMSBindingDeployer JMSBC-E0725: Failed to initialize the service unit {0} from service unit path {1}: {2}
JMSBC-E0750criticalcom.sun.jbi.jmsbc.OutboundMessageProcessor JMSBC-E0750: Failed in reply listener while processing message exchange with ID {0} and exchange pattern {1} due to error: {2}

File BC

AlertCodeSeveritySourceAlert Detail
FILEBC-E00201 Critical com.sun.jbi.filebc.FileBindingDeployer Service unit {0} failed to deploy, an exception was raised. {1}
FILEBC-E00202 Critical com.sun.jbi.filebc.FileBindingDeployer Service unit {0} failed to initialize, an exception was raised. {1}
FILEBC-E00203 Critical com.sun.jbi.filebc.FileBindingDeployer Service unit {0} failed pre-processing (inbound endpoint locks registration), an exception was raised. {1}
FILEBC-E00204 Critical com.sun.jbi.filebc.FileBindingDeployer Service unit {0} failed to start, an exception was raised. {1}
FILEBC-E00205 Critical com.sun.jbi.filebc.FileBindingDeployer Service unit {0} failed to stop, an exception was raised. {1}
FILEBC-E00206 Critical com.sun.jbi.filebc.FileBindingDeployer Service unit {0} failed post-processing after stop, an exception was raised. {1}
FILEBC-E00207 Critical com.sun.jbi.filebc.FileBindingDeployer Service unit {0} failed to shut down, an exception was raised. {1}
FILEBC-E00208 Critical com.sun.jbi.filebc.FileBindingDeployer Service unit {0} failed shutdown post-processing, an exception was raised. {1}
FILEBC-E00102 Warning com.sun.jbi.filebc.FileBindingLifeCycle Status provider MBean registration failed, an exception was raised. {0}
FILEBC-E00103 Warning com.sun.jbi.filebc.FileBindingLifeCycle Configuration MBean registration failed, an exception was raised. {0}
FILEBC-W00126 Critical com.sun.jbi.filebc.FileBindingLifeCycle An exception occurred while attempting to register the management MBean: {0}
FILEBC-E00104 Critical com.sun.jbi.filebc.FileBindingLifeCycle Unable to obtain the delivery channel. {0}
FILEBC-E00105 Critical com.sun.jbi.filebc.FileBindingLifeCycle Outbound message receiver failed to start, an exception was raised. {0}
FILEBC-E00107 Critical com.sun.jbi.filebc.FileBindingLifeCycle Inbound message receiver failed to start, an exceptionw as raised. {0}
FILEBC-E00108 Warning com.sun.jbi.filebc.FileBindingLifeCycle Outbound receiver failed to stop, an exception was raised. {0}
FILEBC-E00109 Warning com.sun.jbi.filebc.FileBindingLifeCycle Status provider MBean deregistration failed, an exception was raised. {0}
FILEBC-E00110 Warning com.sun.jbi.filebc.FileBindingLifeCycle Configuration MBean deregistration failed, an exception was raised. {0}
FILEBC-W00127 Critical com.sun.jbi.filebc.FileBindingLifeCycle An exception occurred while attempting to unregister the management MBean: {0}
FILEBC-R00110 Warning com.sun.jbi.filebc.FileBindingLifeCycle Parsing the JBI descriptor ({0}) failed. Version information for this component is not available. An exception was raised. {1}
FILEBC-E00715 Critical com.sun.jbi.filebc.IBFileWorker Read error: Input file {0} does not exist or may be empty.
FILEBC-E00716 Critical com.sun.jbi.filebc.IBFileWorker Input file {0} failed processing, an exception was raised: {1}
FILEBC-E00717 Critical com.sun.jbi.filebc.IBFileWorker Input file {0} failed processing, has been moved to: {1}. Error details have been written to: {2}.
FILEBC-E00718 Critical com.sun.jbi.filebc.IBFileWorker Attempting to flag input file {0} for error resulted in an exception. {1}
FILEBC-W00807 Warning com.sun.jbi.filebc.IBFileWorker The {0} redelivery on-failure option is not supported for InOut exchanges. The redelivery configuration will be ignored and the message exchange processing will proceed without redelivery attempts.
FILEBC-E00720 Critical com.sun.jbi.filebc.InboundMessageProcessor {0} message for operation {1} failed processing, an exception was raised. {2}
FILEBC-E00724 Critical com.sun.jbi.filebc.InboundMessageProcessor Message exchange reply status specifies an unsupported message exchange pattern of {0}
FILEBC-E00727 Critical com.sun.jbi.filebc.InboundMessageProcessor Archiving processed file {0} failed, renaming it to {1} failed.
FILEBC-E00771 Warning com.sun.jbi.filebc.InboundMessageProcessor Failed to send InOut message
FILEBC-E00739 Warning com.sun.jbi.filebc.OutboundMessageProcessor Robust in-only message exchanges are not supported. Message ID: {0}.
FILEBC-E00740 Warning com.sun.jbi.filebc.OutboundMessageProcessor In-out message exchanges are not supported. Message ID: {0}
FILEBC-E00742 Critical com.sun.jbi.filebc.OutboundMessageProcessor Message processing loop terminated, an exception was raised: {0}
FILEBC-E00741 Warning com.sun.jbi.filebc.OutboundMessageProcessor Message processing loop terminated, an exception was raised: {0}
FILEBC-E00791 Critical com.sun.jbi.filebc.OutboundMessageProcessor Solicited Read Failed. service: {0}, endpoint: {1}, operation: {2}. Error was: {3}.
FILEBC-E00792 Critical com.sun.jbi.filebc.OutboundMessageProcessor Solicited Read Failed. But error message could not be sent to the invoking service due to: {0}.
FILEBC-W00701 Warning com.sun.jbi.filebc.OutboundMessageProcessor Attempt to write a message for service: {0}, endpoint: {1}, operation: {2}, failed. Error was: {4}
FILEBC-W00703 Warning com.sun.jbi.filebc.OutboundMessageProcessor An inbound request-reply message failed to process. An exception was raised. {0}
FILEBC-E00765 Warning com.sun.jbi.filebc.OutboundMessageProcessor Maximum redelivery attempts has been exhausted, endpoint with service name {0} and endpoint name {1} will be suspended as per the configured Re-delivery on-failure option...
FILEBC-E00766 Warning com.sun.jbi.filebc.OutboundMessageProcessor Failed to process the 'suspend' redelivery on-failure option for endpoint with service name {0}, endpoint name {1}: {2}
FILEBC-E00767 Warning com.sun.jbi.filebc.OutboundMessageProcessor Provider for service {0} endpoint {1} responded with an error status. Error detail is: {2}
FILEBC-E00768 Warning com.sun.jbi.filebc.OutboundMessageProcessor Provider for service {0} endpoint {1} responded with an error status. No detail was provided.
FILEBC-E00769 Warning com.sun.jbi.filebc.OutboundMessageProcessor An exception occured while attempting to redeliver a message exchange with message group ID: {0}, message ID: {1}.
FILEBC-E00301 Critical com.sun.jbi.filebc.ServiceUnitImpl Service unit {0} deployment failed, an exception was raised. {1}
FILEBC-W00306 Warning com.sun.jbi.filebc.ServiceUnitImpl There are no endpoints to create. None are listed in the jbi.xml for the {0} service unit {1}.
FILEBC-W00307 Warning com.sun.jbi.filebc.ServiceUnitImpl No {0} web service definition exists for Service Unit {1} to handle.
FILEBC-E00304 Critical com.sun.jbi.filebc.ServiceUnitImpl Service unit {0} initialization failed for service endpoint {1}/{2}, an exception was raised. {3}
FILEBC-E00308 Critical com.sun.jbi.filebc.ServiceUnitImpl Service unit {0} initialization failed, an exception was raised. {1}
FILEBC-E00306 Critical com.sun.jbi.filebc.ServiceUnitImpl Service unit {0} start failed, an exception was raised. {1}
FILEBC-E00307 Critical com.sun.jbi.filebc.ServiceUnitImpl Inbound message processor start failed, an exception was raised. {0}

Database BC

AlertCodeSeveritySourceAlert Detail
DBBC-E01036 Warning org.glassfish.openesb.databasebc.OutboundMessageProcessor An exception occured while attempting to redeliver a message exchange with message group ID: {0}, message ID: {1}.
DBBC-E00720 Warning org.glassfish.openesb.databasebc.OutboundMessageProcessor Provider for service Plugin insertion failed: Could not find plugin 0 endpoint Plugin insertion failed: Could not find plugin 1 responded with an error status. Error detail is: {2}
DBBC-E00721 Warning org.glassfish.openesb.databasebc.OutboundMessageProcessor Provider for service Plugin insertion failed: Could not find plugin 0 endpoint Plugin insertion failed: Could not find plugin 1 responded with an error status. No detail was provided.
DBBC-E00759 Warning org.glassfish.openesb.databasebc.OutboundMessageProcessor An exception occured while processing a reply message. {0}

Scheduler BC

Alert Code Severity Source Alert Detail
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 Critical org.glassfish.openesb.schedulerbc.SchedulerComponentManager Cannot create Quartz Scheduler for Service Assembly {0}
SCHEDBC-7002 Critical org.glassfish.openesb.schedulerbc.SchedulerComponentManager.SchedulerJobFactory Cannot find respective Scheduler endpoint
SCHEDBC-7003 Critical org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint WSDL for Endpoint {0} does not represent a valid Scheduler binding
SCHEDBC-7004 Critical org.glassfish.openesb.schedulerbc.domain.SchedulerEndPoint Cannot initialize Scheduler for endpoint {0}

XSLT SE

Alert Code Severity Source Alert Detail
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}

FTP BC


AlertCode Severity SourceAlert Detail
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-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-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-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-E004033 SEVERE com.sun.jbi.ftpbc.InboundMessageProcessor
 FTPBC-E004033: Inbound message exchange error: status is not DONE, status={0}, message exchange ID={1}
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-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-E004061 SEVERE com.sun.jbi.ftpbc.OutboundMessageProcessor
com.sun.jbi.ftpbc.ResponsePoller
 FTPBC-E004061: Exception when send error during error handling: exception = {0}.
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-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-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-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-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-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-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-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-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-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}.

IEP SE

AlertCodeSeveritySourceAlert Detail
IEPSEaka00000Infocom.sun.jbi.engine.iep.core.runtime.util.alert.IEPSEAlertSenderEngine {0} status changed to {1} at {2}
IEPSEaka00002Majorcom.sun.jbi.engine.iep.core.runtime.util.alert.IEPSEAlertSenderUnable to connect to database at {2}. Engine : {0}, Cause : {1}
IEPSEaka00005Majorcom.sun.jbi.engine.iep.core.runtime.util.alert.IEPSEAlertSenderDB connection restored at {1}. Engine : {0}
IEPSEaka00007Infocom.sun.jbi.engine.iep.core.runtime.util.alert.IEPSEAlertSenderSU {1} on Engine {0} changed status to {2} at {3}

BPEL SE

AlertCodeSeveritySourceAlert Detail
BPCOR-5005Infobpel-jbiadapterEngine {0} status changed to {1} at {2}
BPCOR-5008Infobpel-jbiadapterSU {1} on Engine {0} changed status to {2} at {3}
BPCOR-5006Infobpel-monitoringBusiness process instance variable changed by API at {4}. Engine \: {0}, process\: {1}, instance\: {2}, variable\: {3}
BPCOR-5007Infobpel-monitoringBusiness process instance {3} by API at {4} . Engine \: {0}, process\: {1}, instance\: {2}
BPCOR-6142Majorbpel-coreBusiness process instance terminated on unhandled fault at {4}. Engine \: {0}, process\: {1}, instance\: {2}. Cause \: {3}
BPCOR-6144Majorbpel-coreUnable to connect to database at {2}. Engine \: {0}, Cause \: {1}
BPCOR-6146Majorbpel-coreDB connection restored at {1}. Engine \: {0}
BPCOR-7010Criticalbpel-coreEngine {0} unable to create process instance for \: {1} at {3}. Cause \: {2}

Back to SystemicQualities.Monitoring
G'day, Anonymous Guest

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