|
|
|
HTTPBC-S00800 |
critical |
Failed to process message exchange. Cause:
A generic exception was thrown for problems encountered when processing message exchanges from the
NMR. In most cases, nested exceptions will point to the specific problems. Action: Depending
on the nested exception, different recourse actions may be needed. Check the server log
for additional information. |
HTTPBC-S00801 |
critical |
Failed to accept message exchange from the NMR. This is
not a recoverable error. HTTP Binding Component will stop accepting from NMR. Cause: Something is
seriously wrong in the NMR. Messages cannot be delivered to the HTTP Binding Component
properly. Action: Report the issue immediately. |
HTTPBC-E00720 |
warning |
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} Cause: The HTTP Binding Component got an ERROR
status when processing a message exchange from the NMR. The cause of the
error will be captured in the exception message. Action: Depending on the error itself,
it is best to examine the error message detail before taking any actions. |
HTTPBC-E00721 |
warning |
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. Cause: The HTTP Binding Component got an ERROR status when processing a
message exchange from the NMR, but there is no error detail given by
the component that set the ERROR status. Action: Report the issue. |
HTTPBC-E00751 |
warning |
Message 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-W00758 |
warning |
An exception occurred while processing a request
message. {0} Cause: Encountered an issue when trying to prepare the SOAP request, or
when invoking an external webservice using the SOAP request. There can be a
number of possible causes: denormalization problem, network issues, external service availability issues, and so
forth. Action: Check the server log to determine the actual cause before taking any
recourse actions. |
HTTPBC-E00759 |
warning |
An exception occurred while processing a reply message. {0} Cause: Encountered an
issue when preparing or sending a SOAP response back to the webservice client. There
can be a number of problems: message denormalization error, transport/network issues, and so
forth. Action: Check the server log to determine the actual cause before taking any
recourse actions. |
HTTPBC-E00775 |
warning |
An exception occurred while processing message exchange {0} Cause: Setting an unsupported exchange
pattern on the message exchange. Action: Nothing can be done to recover from
this error, but make sure that only in-only or in-out exchanges are used. |
HTTPBC-E00776 |
critical |
Failed
to create SOAP normalize/denormalizer. {0} Cause: Internal error. HTTP Binding Component is not able
to instantiate the SOAP message normalization or denormalizer. Action: Report the issue. |
HTTPBC-E00777 |
warning |
Failed to create
HTTP normalizer. {0} Cause: The HTTP Binding Component is not able to instantiate the
HTTP binding message normalizer or denormalizer. Action: Report the issue. |
HTTPBC-E00778 |
warning |
Failed to create OutboundMessageProcessor. {0} Cause:
Internal error. HTTP Binding Component is not able to set up the required
environment to process message exchanges. Action: Report the issue. |
HTTPBC-E00779 |
warning |
An exception occurred while attempting
to sending a reply Cause: The HTTP Binding Component is not able to send
an ACK message through the NMR. Action: Nothing can be done, unrecoverable error.
Report the issue. |
HTTPBC-E00780 |
warning |
An exception occurred while attempting to set the status of a
message exchange Cause: The HTTP Binding Component is not able to set a message
exchange status. This can be caused by an illegal state change or NMR
issues. Action: Nothing can be done, report the issue. |
HTTPBC-E00805 |
warning |
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} Cause:
The HTTP Binding Component found a "suspend" on-failure option configured for an in-out
exchange. This is not supported. Action: Do not use a "suspend" on-failure option on
in-out exchanges. |
HTTPBC-E00806 |
warning |
Maximum redelivery attempts have 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 Binding Component is about to suspend the endpoint when all
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-E01036 |
warning |
An exception occurred 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 the issue. |
HTTPBC-E01050 |
warning |
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. Cause: The org.glassfish.openesb.address.url NM property is used
to overwrite the soap:address that is 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-E01051 |
warning |
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}. Cause: The HTTP Binding Component is not able to instantiate the JAX-WS
Dispatch client. There can be issues in the Metro layer. Action: Check the
server log and report an issue. |
HTTPBC-E01052 |
warning |
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. Cause: Found
a non-String type value for the org.glassfish.openesb.address.url NM property. Action: Make sure that
a string representing a valid URL is assigned to the NM property. |
HTTPBC-E00151 |
warning |
Unable to
find component that provisions endpoint {0}. Ensure that the service unit for the
provisioning component has been deployed. Cause: The HTTP Binding Component is not able to
locate the provider for the service endpoint to which it is about to
send the message exchange through the NMR. Action: Make sure that the SA
is deployed and started properly. If everything looks correct but the error persists,
report the issue. |
HTTPBC-E00701 |
warning |
Failed to locate the operation in the requested endpoint {0} that
matches the message signature Cause: the HTTP Binding Component is not able to find
an operation name or information in the SOAP/HTTP request to match 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 a critical problem
that can keep the message from being processed properly. Action: Check the nested validation
error in the server log and fix the validation error accordingly. Note: the
HTTP Binding Component 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
occurred while processing message exchange {0} for {1} Cause: Problems were encountered while processing the
SOAP request. This can be a number of issues including a SOAP message
validation error, JBI normalization error, and so forth. 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. The supported requests 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 is neither SOAP nor a valid text/xml message. Action:
Check the request client to make sure that any request coming to the
ESB 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 that only in-only or in-out
exchanges are used |
HTTPBC-E00771 |
warning |
Failed to send InOnly message Cause: The HTTP Binding Component failed to
send the in-only message exchange to the downstream component through the NMR. Action: Report
the issue. |
HTTPBC-E00772 |
warning |
Failed to send InOut message Cause: The HTTP Binding Component failed to send
the in-out message exchange to the downstream component through the NMR. Action: Report the
issue. |
HTTPBC-E00773 |
warning |
The requested endpoint {0} does not have any defined operations Cause: The HTTP
Binding Component couldn't locate the operation name associated with the SOAP 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 that only 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 Plugin insertion failed: Could not find plugin 0, endpoint name
Plugin insertion failed: Could not find plugin 1: {2} Cause: The HTTP Binding Component 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: The 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: The HTTP Binding Component 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: The HTTP Binding Component 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: The
HTTP Binding Component is not able to locate the component descriptor file in
order to perform the component startup operation. Action: Report the issue. |
HTTPBC-E00154 |
warning |
Failed to create a
Document Builder to parse the descriptor file for identity information; descriptor file is
{0} Cause: Internal error. HTTP Binding Component 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 captures all of the HTTP Binding Component
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 that the component is shutting down. Action: Nothing. |
HTTPBC-R00105 |
info |
{0}
stopped Cause: Normal lifecycle informational message to indicate that the component is being stopped. Action:
Nothing. |
HTTPBC-E00104 |
critical |
Failed to stop {0}. {1} Cause: The HTTP Binding Component failed to stop. This
can be caused by a number of issues. Action: Report an issue. |
HTTPBC-W00120 |
critical |
An exception
occurred while attempting to register the status provider MBean: {0} Cause: The HTTP Binding
Component is not able to register the Statistics MBean. Action: Report the issue. |
HTTPBC-W00121 |
critical |
An
exception occurred while attempting to register the extension MBean: {0} Cause: The HTTP Binding
Component is not able to register the required extension MBean. Action: Report the issue. |
HTTPBC-W00122 |
critical |
An
exception occurred while attempting to register the runtime configuration MBean: {0} Cause: The HTTP
Binding Component is not able to register the runtime configuration MBean. Action: Report the
issue. |
HTTPBC-W00123 |
critical |
An exception occurred while attempting to deregister the status provider MBean: {0} Cause: The
HTTP Binding Component is not able to unregister the Statistics MBean when it
is shutting down. Action: Report the issue. |
HTTPBC-W00124 |
warning |
An exception occurred while attempting to unregister the
extension MBean: {0} Cause: The HTTP Binding Component is not able to unregister the extension
MBean when it is shutting down. Action: Report the issue. |
HTTPBC-W00125 |
critical |
An exception occurred while attempting
to unregister the runtime configuration MBean: {0} Cause: The HTTP Binding Component is not able
to unregister the runtime configuration MBean when it is shutting down. Action: Report the
issue. |
HTTPBC-W00126 |
critical |
An exception occurred while attempting to register the management MBean: {0} Cause: The HTTP
Binding Component is not able to register the endpoint monitoring/management MBean. Action: Report the
issue. |
HTTPBC-W00127 |
critical |
An exception occurred while attempting to unregister the management MBean: {0} Cause: The HTTP
Binding Component is not able to unregister the endpoint monitoring/management MBean when it is
shutting down. Action: Report the issue. |
HTTPBC-W01303 |
info |
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 resume() call will be ignored. Cause: The
HTTP Binding Component is not able to locate the endpoint name specified for
the "resume" operation. Action: Double check the endpoint name to ensure that it is
a valid endpoint name that the HTTP Binding Component provides services 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 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: The HTTP Binding Component is not able to locate the endpoint
name specified for the "suspend" operation. Action: Double check the endpoint name to ensure
that it is a valid endpoint name that the HTTP Binding Component provides
services 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 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: The HTTP Binding Component is not able
to locate the endpoint name specified for the "isEndpointActive" operation. Action: Double check
the endpoint name to ensure that it is a valid endpoint name that
the HTTP Binding Component provides services 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 Plugin insertion failed: Could not find plugin
0 is not a consumer endpoint. Cause: The endpoint name passed to the "resume" operation
does not apply to an endpoint for which the HTTP Binding Component
provides service. Action: Double check the endpoint name to ensure that it is
a valid endpoint name that the HTTP Binding Component 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 Plugin insertion
failed: Could not find plugin 0 is not a consumer endpoint. Cause: The endpoint
name passed to the "suspend" operation does not apply to an endpoint for which
the HTTP Binding Component provides service. Action: Double check the endpoint name to
ensure that it is a valid endpoint name that the HTTP Binding Component
provides services for before passing it as an argument to the "suspend" operation. |
HTTPBC-E00201 |
critical |
Deployment
failed. {0} Cause: The HTTP Binding Component failed to deploy the application. There can
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 is an
HTTP Binding Component issue, report the problem. |
HTTPBC-E00203 |
critical |
Initialization failed. {0} Cause: The HTTP Binding
Component failed to perform the init() lifecycle call on the application. There can 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
is an HTTP Binding Component issue, report the problem. |
HTTPBC-E00205 |
critical |
Start failed. {0} Cause: The HTTP
Binding Component failed to perform the start() lifecycle call on the application. There can
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 is an HTTP Binding Component issue, report the problem. |
HTTPBC-E00206 |
critical |
Stop failed Cause: The HTTP
Binding Component failed to stop the application. There can 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 is an HTTP Binding
Component issue, report the problem. |
HTTPBC-E00210 |
critical |
Shutdown failed Cause: The HTTP Binding Component failed to shut
down the application. There can 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 is an HTTP Binding Component issue,
report the problem. |
HTTPBC-W00671 |
warning |
An exception occurred while attempting to resolve endpoint reference. Cause: The HTTP
Binding Component failed to resolve the addressing document and retrieve the endpoint reference information
in order to perform the dynamic EPR callback. Action: Double check the addressing document
to ensure that it is valid and that the format is supported (based
on WS-Addressing Member Submission version). |
HTTPBC-E01028 |
warning |
Failed to load Access Manager configuration properties file {0}:
{1} Cause: The HTTP Binding Component is not able to read the Access Manager
configuration file. Action: Make sure the Access Manager configuration file is at the configured location,
and it contains the proper AM configurations used in the properties (i.e. name=value). |
HTTPBC-E01041 |
warning |
Unable
to find the Access Manager configuration properties file {0} in directory {1} Cause: The
HTTP Binding Component is not able to find the Access Manager configuration file Action:
Make sure the Access Manager configuration file is at the configured location .
If it is and the same error persists, report an issue. |