Index Changes
This is version 13. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

GlassFish ESB Alert Codes and Error Messages

Note - This document is a work in progress.

Contents

HTTP BC Alert Codes

Alert CodeSeverityAlert Text - Cause - Action
HTTPBC-S00800criticalFailed to process message exchange

Cause: A generic exception thrown for problems encountered when processing message exchanges from the NMR. In most cases, there will be nested exception(s) pointing to the specific problems.
Action: Depending on the nested exception, different recourse actions may be needed. It's best to check the server log.
HTTPBC-S00801criticalFailed to accept message exchange from the NMR. This is not a recoverable error. HTTP BC will stop accepting from NMR.

Cause: Something really wrong in the NMR. Messages cannot be delivered to HTTP BC properly
Action: Report an issue right away.
HTTPBC-E00720warningProvider 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}

Cause: HTTP BC got an ERROR status when processing a message exchange from the NMR. Cause of the error will be captured in the exception message.
Action: Depending on the error itself, it's best to examine the error detail message before taking any actions.
HTTPBC-E00721warningProvider 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.

Cause: HTTP BC got an ERROR status when processing a message exchange from the NMR but there is no error detail given by the component setting the ERROR status
Action: Report the issue
HTTPBC-E00751warningMessage exchange {0} cannot be processed because its exchange pattern, robust in-only, is not supported

Cause: Robust in-only is not a supported exchange pattern.
Action: Make sure the HTTP/SOAP WSDL has either an in-only or in-out exchange pattern. See JBI 1.1 specification or WSDL 1.1 specification for details on exchange patterns.
HTTPBC-W00758warningAn exception occured while processing a request message. {0}

Cause: Encountered an issue when trying to prepare the SOAP request, or invoking an external webservice using the SOAP request. There could be a number of possible causes: denormalization problem, network issues, external service availability issues etc
Action: Check the server log to determine the actual cause before taking any recourse actions
HTTPBC-E00759warningAn exception occured while processing a reply message. {0}

Cause: Encountered an issue when preparing and/or sending a SOAP response back to the webservice client. There could be a number of problems: message denormalization error, transport/network issues etc.
Action: Check the server log to determine the actual cause before taking any recourse actions
HTTPBC-E00775warningAn exception occured while processing message exchange {0}

Cause: Error when setting an unsupported exchange pattern ERROR on the message exchange
Action:Nothing can be done to recover from the error, but make sure in-only or in-out exchanges are used.
HTTPBC-E00776criticalFailed to create SOAP normalize/denormalizer. {0}

Cause: Internal error. HTTP BC is not able to instantiate the SOAP message normalization or denormalizer
Action: Report the issue
HTTPBC-E00777warningFailed to create HTTP normalizer. {0}

Cause: HTTP BC is not able to instantiate the HTTP binding message normalizer or denormalizer
Action: Report the issue
HTTPBC-E00778warningFailed to create OutboundMessageProcessor. {0}

Cause: Internal error. HTTP BC is not able to set up the required environment to process message exchanges
Action: Report the issue
HTTPBC-E00779warningAn exception occured while attempting to sending a reply

Cause: HTTP BC is not able to send an ACK message through the NMR
Action: Nothing can be done, unrecoverable error. Report an issue
HTTPBC-E00780warningAn exception occured while attempting to set the status of a message exchange

Cause: HTTP BC is not able to set a message exchange status. Could be caused by an illegal state change or NMR issues.
Action: Nothing can be done, report an issue
HTTPBC-E00805warningFailed 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}

Cause: HTTP BC found a "suspend" on-failure option configured for an in-out exchange. That is not supported
Action: Do not use "suspend" on-failure option on in-out exchanges.
HTTPBC-E00806warningMaximum 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...

Cause: Informational warning message. HTTP BC is about to suspend the endpoint when the retries are exhausted.
Action: Nothing needs to be done. This is a warning message just to let the user know the endpoint is about to be suspended
HTTPBC-E01036warningAn exception occured while attempting to redeliver a message exchange with message group ID: {0}, message ID: {1}.

Cause: Found an error trying to redeliver a message exchange.
Action: Check the server log and report an issue
HTTPBC-E01050warningReceived 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.

Cause: The org.glassfish.openesb.address.url NM property is used to overwrite the soap:address to be used to invoke an external service, but the NM property doesn't have a valid URL value
Action: Make sure a valid URL is assigned to the NM property
HTTPBC-E01051warningFailed 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}.

Cause: HTTP BC is not able to instantiate the JAX-WS Dispatch client. There could be issues in the Metro layer
Action: Check the server log and report an issue
HTTPBC-E01052warningThe value set on the org.glassfish.openesb.address.url normalized message property is invalid. This property is expected to be of String type only.

Cause: Found a non-String type value for the org.glassfish.openesb.address.url NM property.
Action: Make sure a string representing a valid URL is assigned to the NM property
HTTPBC-E00151warningUnable to find component that provisions endpoint {0}. Ensure that the service unit for the provisioning component has been deployed.

Cause: HTTP BC is not able to locate the provider for the service endpoint it's about to send the message exchange to through the NMR
Action: Make sure the SA is deployed and started properly. If everything looks good, but the error persists, report an issue
HTTPBC-E00701warningFailed to locate the operation in the requested endpoint {0} that matches the message signature

Cause:
Action:
HTTPBC-E00741criticalSOAP message validator error: {0}

Cause:
Action:
HTTPBC-E00748warningAn exception occured while processing message exchange {0} for {1}

Cause:
Action:
HTTPBC-E00749warningInvalid/unsupported HTTP verb encountered: {0}

Cause:
Action:
HTTPBC-E00750warningUnsupported message type: {0}

Cause:
Action:
HTTPBC-E00751warningMessage exchange {0} cannot be processed because its exchange pattern, robust in-only, is not supported

Cause:
Action:
HTTPBC-E00771warningFailed to send InOnly message

Cause:
Action:
HTTPBC-E00772warningFailed to send InOut message

Cause:
Action:
HTTPBC-E00773warningThe requested endpoint {0} does not have any defined operations

Cause:
Action:
HTTPBC-E00774warningMessage Exchange Pattern {0} is invalid for endpoint {1}

Cause:
Action:
HTTPBC-E00805warningFailed 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}

Cause:
Action:
HTTPBC-E00101critical{0} failed to start. {1}

Cause:
Action:
HTTPBC-E00141criticalCannot obtain binding channel from context. {0}

Cause:
Action:
HTTPBC-E00152warningFailed to parse the descriptor file for identity information; file descriptor file is {0}

Cause:
Action:
HTTPBC-E00153warningFailed to read the descriptor file for identity information; descriptor file is {0}

Cause:
Action:
HTTPBC-E00154warningFailed to create a DocumentBuilder to parse the descriptor file for identity information; descriptor file is {0}

Cause:
Action:
HTTPBC-R00101info{0} started with the following configuration:

Cause:
Action:
HTTPBC-R00103info{0} shut down

Cause:
Action:
HTTPBC-R00105info{0} stopped

Cause:
Action:
HTTPBC-E00104criticalFailed to stop {0}. {1}

Cause:
Action:
HTTPBC-W00120criticalAn exception occurred while attempting to register the status provider MBean: {0}

Cause: HTTP BC is not able to register the Statistics MBean
Action: Report an issue
HTTPBC-W00121criticalAn exception occurred while attempting to register the extension MBean: {0}

Cause: HTTP BC is not able to register the required extension MBean
Action: Report an issue
HTTPBC-W00122criticalAn exception occurred while attempting to register the runtime configuration MBean: {0}

Cause: HTTP BC is not able to register the runtime configuration MBean
Action: Report an issue
HTTPBC-W00123criticalAn exception occurred while attempting to unregister the status provider MBean: {0}

Cause: HTTP BC is not able to unregister the Statistics MBean whe it's shutting down
Action: Report an issue
HTTPBC-W00124warningAn exception occurred while attempting to unregister the extension MBean: {0}

Cause: HTTP BC is not able to unregister the extension MBean whe it's shutting down
Action: Report an issue
HTTPBC-W00125criticalAn exception occurred while attempting to unregister the runtime configuration MBean: {0}

Cause: HTTP BC is not able to unregister the runtime configuration MBean whe it's shutting down
Action: Report an issue
HTTPBC-W00126criticalAn exception occurred while attempting to register the management MBean: {0}

Cause: HTTP BC is not able to register the endpoint monitoring/management MBean
Action: Report an issue
HTTPBC-W00127criticalAn exception occurred while attempting to unregister the management MBean: {0}

Cause: HTTP BC is not able to unregister the endpoint monitoring/management MBean when it's shutting down
Action: Report an issue
HTTPBC-W01303infosun-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...

Cause:
Action:
HTTPBC-W01304criticalsun-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...

Cause:
Action:
HTTPBC-W01305infosun-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...

Cause:
Action:
HTTPBC-W01306inforesume() 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.

Cause:
Action:
HTTPBC-W01307infosuspend() 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.

Cause:
Action:
HTTPBC-E00201criticalDeployment failed. {0}

Cause:
Action:
HTTPBC-E00203criticalInitialization failed. {0}

Cause:
Action:
HTTPBC-E00205criticalStart failed. {0}

Cause:
Action:
HTTPBC-E00206criticalStop failed

Cause:
Action:
HTTPBC-E00210criticalShutdown failed

Cause:
Action:
HTTPBC-W00671warningAn exception occured while attempting to resolve endpoint reference.

Cause:
Action:
HTTPBC-E01028warningFailed to load Sun Access Manager configuration properties file {0}: {1}

Cause:
Action:
HTTPBC-E01041warningUnable to find the Access Manager configuration properties file {0} in directory {1}

Cause:
Action:



Previous Next


Return to the GlassFish Documentation Home Page

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This particular version was published on 03-Sep-09 17:56 PM, -0700 by Sherry Weng