Index Changes

Difference between version and version     

Back to HTTPBC Alert Codes, or HTTPBC Alert Codes Info


At line 20 added 1 line.
** [TransformSL Logging Codes]
At line 25 changed 1 line.
* [JBI Runtime Error Messages|JBIRuntimeMessages]\\
* [JBI Runtime Error Messages|JBIRuntimeMessages]
GlassFish ESB v2.2 Components
* [Email BC Logging Codes]
* [HL7 Encoder Logging Codes]
* [POJO SE Logging Codes]
* [HL7BC Alert Codes]
* [REST BC Logging Codes]\\
At line 52 changed 20 lines.
|__HTTPBC-E00701__|warning|__Failed to locate the operation in the requested endpoint {0} that matches the message signature__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00741__|critical|__SOAP message validator error: {0}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00748__|warning|__An exception occured while processing message exchange {0} for {1}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00749__|warning|__Invalid/unsupported HTTP verb encountered: {0}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00750__|warning|__Unsupported message type: {0}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00751__|warning|__Message exchange {0} cannot be processed because its exchange pattern, robust in-only, is not supported__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00771__|warning|__Failed to send InOnly message__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00772__|warning|__Failed to send InOut message__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00773__|warning|__The requested endpoint {0} does not have any defined operations__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00774__|warning|__Message Exchange Pattern {0} is invalid for endpoint {1}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00805__|warning|__Failed to process the 'suspend' redelivery on-failure option for endpoint with service name [{0}], endpoint name [{1}]: {2}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00101__|critical|__{0} failed to start. {1}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00141__|critical|__Cannot obtain binding channel from context. {0}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00152__|warning|__Failed to parse the descriptor file for identity information; file descriptor file is ''{0}''__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00153__|warning|__Failed to read the descriptor file for identity information; descriptor file is ''{0}''__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00154__|warning|__Failed to create a DocumentBuilder to parse the descriptor file for identity information; descriptor file is ''{0}''__\\ \\__Cause__: \\__Action__:
|__HTTPBC-R00101__|info|__{0} started with the following configuration:__\\ \\__Cause__: \\__Action__:
|__HTTPBC-R00103__|info|__{0} shut down__\\ \\__Cause__: \\__Action__:
|__HTTPBC-R00105__|info|__{0} stopped__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00104__|critical|__Failed to stop {0}. {1}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00701__|warning|__Failed to locate the operation in the requested endpoint {0} that matches the message signature__\\ \\__Cause__: HTTP BC is not able to find the operation name/information in the SOAP/HTTP request that matches the WSDL definition \\__Action__: Double check the request message to make sure it matches the service definition
|__HTTPBC-E00741__|critical|__SOAP message validator error: {0}__\\ \\__Cause__: The SOAP request has some kind of critical problem that will keep the message from being processed properly \\__Action__: Check the nested validation error in the server log and fix the validation error accordingly. Note: HTTP BC is WS-I basic profile compliant but it also allows for legacy SOAP message exchanges, such as RPC-encoded, doc-literal with complex type messages.
|__HTTPBC-E00748__|warning|__An exception occured while processing message exchange {0} for {1}__\\ \\__Cause__: A generic exception pointing to problems encountered while processing the SOAP request. This could be a number of issues including SOAP message validation error, JBI normalization error etc.\\__Action__: Check the nested exception that has the detailed description of the specific problem.
|__HTTPBC-E00749__|warning|__Invalid/unsupported HTTP verb encountered: {0}__\\ \\__Cause__: Encountered an unsupported HTTP operation. Supported ones are: POST and GET \\__Action__: Make sure the HTTP client sends either a GET or POST request. For any other operation mode, use the REST binding component instead.
|__HTTPBC-E00750__|warning|__Unsupported message type: {0}__\\ \\__Cause__: Got a request message that's neither SOAP nor a valid text/xml message \\__Action__: Check the request client to make sure that the request coming to OpenESB conforms to the corresponding WSDL definition
|__HTTPBC-E00751__|warning|__Message exchange {0} cannot be processed because its exchange pattern, robust in-only, is not supported__\\ \\__Cause__: Unsupported message exchange pattern: robust in-only \\__Action__: Modify the WSDL definition to make sure in-only or in-out exchanges are used
|__HTTPBC-E00771__|warning|__Failed to send InOnly message__\\ \\__Cause__: HTTP BC failed to send the in-only message exchange to the downstream component through NMR \\__Action__: Report the issue
|__HTTPBC-E00772__|warning|__Failed to send InOut message__\\ \\__Cause__: HTTP BC failed to send the in-out message exchange to the downstream component through NMR \\__Action__: Report the issue
|__HTTPBC-E00773__|warning|__The requested endpoint {0} does not have any defined operations__\\ \\__Cause__: HTTP BC couldn't locate the operation name associated with the SOAP and/or HTTP message\\__Action__: Double check the WSDL definition to make sure a valid operation name is specified
|__HTTPBC-E00774__|warning|__Message Exchange Pattern {0} is invalid for endpoint {1}__\\ \\__Cause__: Found an invalid message exchange pattern used in the service WSDL. Supported ones are: in-out and in-only \\__Action__:Double check the service WSDL to make sure only in-out and in-only exchange patterns are used
|__HTTPBC-E00805__|warning|__Failed to process the 'suspend' redelivery on-failure option for endpoint with service name [{0}], endpoint name [{1}]: {2}__\\ \\__Cause__: HTTP BC failed to perform the "suspend" operation on the named endpoint. This is for the endpoint which has the "suspend" redelivery on-failure option configured \\__Action__: Report the issue.
|__HTTPBC-E00101__|critical|__{0} failed to start. {1}__\\ \\__Cause__: HTTP binding component cannot be started \\__Action__: Check the server log for the reason why the component cannot be started and report the issue
|__HTTPBC-E00141__|critical|__Cannot obtain binding channel from context. {0}__\\ \\__Cause__: HTTP BC is not able to obtain the service delivery channel (NMR) \\__Action__: Nothing can be done on the application side. Report the issue.
|__HTTPBC-E00152__|warning|__Failed to parse the descriptor file for identity information; file descriptor file is ''{0}''__\\ \\__Cause__: HTTP BC failed to parse the component identification portion of the component descriptor file \\__Action__:Report the issue.
|__HTTPBC-E00153__|warning|__Failed to read the descriptor file for identity information; descriptor file is ''{0}''__\\ \\__Cause__: HTTP BC is not able to locate and/or the component descriptor file in order to perform the component startup operation \\__Action__: Report the issue
|__HTTPBC-E00154__|warning|__Failed to create a DocumentBuilder to parse the descriptor file for identity information; descriptor file is ''{0}''__\\ \\__Cause__: Internal error. HTTP BC is not able to instantiate the DOM parser to parse the component descriptor file \\__Action__:Report the issue
|__HTTPBC-R00101__|info|__{0} started with the following configuration:__\\ \\__Cause__: Normal informational message. This will capture all the HTTP BC configurations and default values if applicable in the server log \\__Action__:Nothing
|__HTTPBC-R00103__|info|__{0} shut down__\\ \\__Cause__: Normal lifecycle informational message to indicate the component is shutting down \\__Action__: Nothing
|__HTTPBC-R00105__|info|__{0} stopped__\\ \\__Cause__: Normal lifecycle informational message to indicate the component is being stopped \\__Action__: Nothing
|__HTTPBC-E00104__|critical|__Failed to stop {0}. {1}__\\ \\__Cause__: HTTP BC failed to stop. This could be caused by a number of issues \\__Action__:Report an issue
At line 80 changed 14 lines.
|__HTTPBC-W01303__|info|__sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID [{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-W01304__|critical|__sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID [{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-W01305__|info|__sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID [{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-W01306__|info|__resume() operation only applies to inbound(consuming) endpoints. Ignoring current resume() request because endpoint with the ID of [{0}] is not a consumer endpoint.__\\ \\__Cause__: \\__Action__:
|__HTTPBC-W01307__|info|__suspend() operation only applies to inbound(consuming) endpoints. Ignoring current suspend() request because endpoint with the ID of [{0}] is not a consumer endpoint.__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00201__|critical|__Deployment failed. {0}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00203__|critical|__Initialization failed. {0}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00205__|critical|__Start failed. {0}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00206__|critical|__Stop failed__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E00210__|critical|__Shutdown failed__\\ \\__Cause__: \\__Action__:
|__HTTPBC-W00671__|warning|__An exception occured while attempting to resolve endpoint reference.__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E01028__|warning|__Failed to load Sun Access Manager configuration properties file ''{0}'': {1}__\\ \\__Cause__: \\__Action__:
|__HTTPBC-E01041__|warning|__Unable to find the Access Manager configuration properties file ''{0}'' in directory ''{1}''__\\ \\__Cause__: \\__Action__:
|__HTTPBC-W01303__|info|__sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID [{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__: HTTP BC is not able to locate the endpoint name specified for the "resume" operation. \\__Action__: Double check the endpoint name to make sure it is a valid endpoint name HTTP BC provides for before passing it as an argument to the "resume" operation
|__HTTPBC-W01304__|critical|__sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID [{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__: HTTP BC is not able to locate the endpoint name specified for the "suspend" operation. \\__Action__: Double check the endpoint name to make sure it is a valid endpoint name HTTP BC provides for before passing it as an argument to the "suspend" operation
|__HTTPBC-W01305__|info|__sun-http-binding is unable to locate an inbound (consuming) endpoint for endpoint ID [{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__: HTTP BC is not able to locate the endpoint name specified for the "isEndpointActive" operation. \\__Action__: Double check the endpoint name to make sure it is a valid endpoint name HTTP BC provides for before passing it as an argument to the "isEndpointActive" operation
|__HTTPBC-W01306__|info|__resume() operation only applies to inbound(consuming) endpoints. Ignoring current resume() request because endpoint with the ID of [{0}] is not a consumer endpoint.__\\ \\__Cause__: The endpoint name passed to the "resume" operation is not for an endpoint HTTP BC provides the service for. \\__Action__: Double check the endpoint name to make sure it is a valid endpoint name HTTP BC provides services for before passing it as an argument to the "resume" operation
|__HTTPBC-W01307__|info|__suspend() operation only applies to inbound(consuming) endpoints. Ignoring current suspend() request because endpoint with the ID of [{0}] is not a consumer endpoint.__\\ \\__Cause__: The endpoint name passed to the "suspend" operation is not for an endpoint HTTP BC provides the service for. \\__Action__: Double check the endpoint name to make sure it is a valid endpoint name HTTP BC provides services for before passing it as an argument to the "suspend" operation
|__HTTPBC-E00201__|critical|__Deployment failed. {0}__\\ \\__Cause__: HTTP BC failed to deploy the application. There could be a number of reasons for the failure. \\__Action__: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and redeploy the application again. If it's an HTTP BC issue, report the problem.
|__HTTPBC-E00203__|critical|__Initialization failed. {0}__\\ \\__Cause__: HTTP BC failed to perform the init() lifecycle call on the application. There could be a number of reasons for the failure. \\__Action__: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and redeploy or restart the application again. If it's an HTTP BC issue, report the problem.
|__HTTPBC-E00205__|critical|__Start failed. {0}__\\ \\__Cause__: HTTP BC failed to perform the start() lifecycle call on the application. There could be a number of reasons for the failure. \\__Action__: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and redeploy or restart the application again. If it's an HTTP BC issue, report the problem.
|__HTTPBC-E00206__|critical|__Stop failed__\\ \\__Cause__: HTTP BC failed to stop the application. There could be a number of reasons for the failure. \\__Action__: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and try to stop the application again. If it's an HTTP BC issue, report the problem.
|__HTTPBC-E00210__|critical|__Shutdown failed__\\ \\__Cause__: HTTP BC failed to shut down the application. There could be a number of reasons for the failure. \\__Action__: Check the nested exception message in the server log. If it is an application error, fix it according to the exception message and try to shut down the application again. If it's an HTTP BC issue, report the problem.
|__HTTPBC-W00671__|warning|__An exception occured while attempting to resolve endpoint reference.__\\ \\__Cause__: HTTP BC failed to resolve the addressing document to retrieve teh endpoint reference information in order to perform the dynamic EPR callback \\__Action__:Double check the addressing document to make sure it is valid and the supported format (based on WS-Addressing Member Submission version)
|__HTTPBC-E01028__|warning|__Failed to load Sun Access Manager configuration properties file ''{0}'': {1}__\\ \\__Cause__: HTTP BC is not able to read the Access Manager configuration file\\__Action__: Make sure the Access Manager configuration file is at the location configured and it contains the proper AM configurations in the properties format (i.e. name=value).
|__HTTPBC-E01041__|warning|__Unable to find the Access Manager configuration properties file ''{0}'' in directory ''{1}''__\\ \\__Cause__: HTTP BC is not able to find the Access Manager configuration file\\__Action__: Make sure the Access Manager configuration file is at the location configured. If it is and the same error persists, report an issue

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