|
HL7BC-E0152
|
Critical
|
Cannot get Delivery Channel from context \: {0}
Cause: An error occurred
while obtaining a delivery channel for the component.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-E0153
|
Critical
|
Failed to start the outbound receiver \: {0}
Cause: An error occurred
when component life cycle start() was called and the JBI container
was starting outbound receivers. Starting the component failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-E0154
|
Critical
|
Failed to start the inbound receiver \: {0}
Cause: An error occurred
when the component life cycle start() was called and the JBI container
was starting inbound receivers. Starting the component failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-W0107
|
Warning
|
Failed to stop the inbound receiver \: {0}
Cause: An error occurred
when the component life cycle stop() was called and the JBI container
was stopping inbound receivers. Stopping the component failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-W0108
|
Warning
|
Failed to stop the outbound receiver \: {0}
Cause: An error occurred
when the component life cycle stop() was called and the JBI container
was stopping outbound receivers. Stopping the component failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-E0155
|
Critical
|
Failed to register status provider MBean. An exception was raised
\:{0v}
Cause: An error occurred
while registering an MBean for collecting message exchange statistics,
and component initialization failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-E0156
|
Critical
|
Failed to register configuration MBean. An exception was raised\:
{0}
Cause: An error occurred
while registering an MBean for runtime configuration, and component
initialization failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-E0157
|
Critical
|
Failed to register Administration MBean. An exception was raised\:
{0}
Cause: An error occurred
while registering an MBean for component administration (list endpoints,
suspend, resume endpoints, and so on). Component initialization failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-W0109
|
Warning
|
Failed to un-register status provider MBean for {0}. An exception
was raised\: {1}
Cause: An error occurred
when component life cycle shutdown() was called and while the JBI
container was unregistering a status provider MBean (collecting message
exchange statistics) associated with the component. Shutting down
the component failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component. You may need to uninstall and install
the component to bring the it to a consistent state.
|
|
HL7BC-W0110
|
Warning
|
Failed to un-register runtime configuration MBean for {0}. An
exception was raised\: {1}
Cause: An error occurred
when component life cycle shutdown() was called and while the JBI
container was unregistering a runtime configuration MBean associated
with the component. Shutting down the component failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component. You may need to uninstall and install
the component to bring the it to a consistent state.
|
|
HL7BC-W0111
|
Warning
|
Failed to un-register Administration MBean for {0}. An exception
was raised\: {1}
Cause: An error occurred
when component life cycle shutdown() was called and while the JBI
container was unregistering a component management MBean (list endpoints,
suspend, and resume component outbound processors) associated with
the component. Shutting down the component failed.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component. You may need to uninstall and install
the component to bring the it to a consistent state.
|
|
HL7BC-W0112
|
Warning
|
Parsing the JBI descriptor ({0}) failed. Version information
for this component is not available. An exception was raised. {1}
Cause: A SAXException was
caught when parsing descriptive information from /META-INF/jbi.xml of the component. This occurs at the end of the component
lifecycle start().
Action: This warning alone
does not affect the component lifecycle since the descriptive information
dumping is for information only, but check the component status and
server log for other fatal errors to make sure the component is started
and running.
|
|
HL7BC-E0158
|
|
Service unit {0} failed to deploy, an exception was raised.
{1}
Cause: An exception was caught
during service unit deployment.
Action: Take one of the following
actions, depending on the error: (1) (1.1) (1.2)
-
If there is an Application Variable or Application
Configuration resolution error, check the corresponding application
variable definitions and application configuration definitions on
the target application server. Also check the tokens in related WSDL
documents for any undefined application variables or application configurations,
or for any mismatch of references and their definitions.
-
For other exceptions, check the error details in the
server log to determine how to correct the error.
|
|
HL7BC-E0159
|
Critical
|
Failed to initialize service unit {0} due to \
Cause: An exception was caught
during service unit initialization.
Action: Take one of the following
actions, depending on the error:
-
For an endpoint validation error, such as endpoint
uniqueness checking, reconfigure the endpoint accordingly.
-
If service unit initialization throws the exception:
-
For an Application Configuration resolution error,
check the application configuration definition on the target application
server and corresponding references.
-
For an encoder reference error, check the message
encoded settings for the endpoint (operation) and the availability
of the corresponding encoder library.
-
For other exceptions, check the error details in the
server log to determine how to correct the error.
|
|
HL7BC-E0160
|
Critical
|
Service unit {0} failed to shut down, an exception was raised.
{1}
Cause: An exception was caught
while shutting down the service unit.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-E0161
|
Critical
|
Service unit {0} failed to start, an exception was raised. {1}
Cause: An exception was caught
while starting the service unit.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component. For a port already in use error,
make sure the configured port used for the inbound service unit does
not conflict with the ports that are already in use.
|
|
HL7BC-E0162
|
Critical
|
Service unit {0} failed to stop, an exception was raised. {1}
Cause: An exception was caught
while stopping the service unit.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component.
|
|
HL7BC-E0179
|
Critical
|
Failed to deploy service unit {0} due to \: {1}
Cause: An exception was caught
when deploy() was called for the service unit. The root cause is most
likely either a service unit descriptor parsing error (corrupted descriptor)
or an application variable loading error.
Action: Check the error details
in the server log to determine how to correct the error, and then
redeploy or restart the component. This error is handled by higher-level
error handling than HL7BC-E0158.
|
|
HL7BC-W0116
|
Warning
|
The service unit {0} does not contain any WSDL(s) for which
the HL7 Binding Component is responsible
Cause: The WSDL document
in use does not contain a service definition.
Action: Verify the service
in the corresponding HL7 service WSDL document.
|
|
HL7BC-E0180
|
Critical
|
Failed to Initialize the end point with service name {0} and
endpoint name {1} \: {2}
Cause:
Action:
|
|
HL7BC-E0181
|
Critical
|
Failed to Initialize the null end point with service name {0}
and exception is \= {1}
Cause:
Action:
|
|
HL7BC-E0182
|
Critical
|
Failed to start the end point with service name {0} and endpoint
name {1} \: {2}
Cause:
Action:
|
|
HL7BC-E0183
|
Critical
|
Failed to start the null end point with service name {0} and
exeption is {1}
Cause:
Action:
|
|
HL7BC-E0184
|
Critical
|
Failed to start inbound message processor for endpoint \: {0}
Cause:
Action:
|
|
HL7BC-E0325
|
Critical
|
Failed to register Connection Monitor MBean. An exception was
raised \:{0}
Cause:
Action:
|
|
HL7BC-W0130
|
Warning
|
Failed to un-register Connection Monitor MBean for {0}. An exception
was raised\: {1}
Cause:
Action:
|
|
HL7BC-W0106
|
Warning
|
Failed to obtain state of service endpoint {0},{1} during attempted
enumeration of inactive endpoints
Cause:
Action:
|
|
HL7BC-W0105
|
Warning
|
Failed to obtain state of service endpoint {0},{1} during attempted
enumeration of active endpoints
Cause:
Action:
|
|
HL7BC-W0005
|
Warning
|
About to suspend endpoint\: serviceName\= {0}, endpointName\={1}.
Cause:
Action:
|
|
HL7BC-E0190
|
Critical
|
MBeanException caught when try to suspend endpoint (redelivery)\:
serviceName\= {0}, endpointName\= {1}, error message\={2}.
Cause:
Action:
|
|
HL7BC-E0016
|
Critical
|
Failed to create HL7 Normalizer due to error\={0}
Cause:
Action:
|
|
HL7BC-E0194
|
Critical
|
Unable to locate a {0} endpoint with name {1} of service {2};
fail on processing message exchange with ID {3}
Cause:
Action:
|
|
HL7BC-E0195
|
Critical
|
Fail to process message exchange with ID {0} as the endpoint
with name {1} of service {2} is in suspended state
Cause:
Action:
|
|
HL7BC-E0201
|
Critical
|
Failed to set the status on the message exchange with ID {0}
and pattern {1} due to error\: {2}
Cause:
Action:
|
|
HL7BC-E0202
|
Critical
|
Failed to send the message exchange with ID {0} and pattern
{1} on the delivery channel due to error\: {2}
Cause:
Action:
|
|
HL7BC-E0203
|
Critical
|
Received the following error on the message exchange with ID
{0} and pattern {1}\: {2}
Cause:
Action:
|
|
HL7BC-E0204
|
Critical
|
Failed in reply listener while processing message exchange with
ID {0} and exchange pattern {1} due to error\: {2}
Cause:
Action:
|
|
HL7BC-E0209
|
Critical
|
Failed to process the message exchange with ID {0} and exchange
pattern {1} due to error\: {2}
Cause:
Action:
|
|
HL7BC-W0119
|
Warning
|
About to suspend endpoint\: serviceName\= {0}, endpointName\=
{1}.
Cause:
Action:
|
|
HL7BC-E0332
|
Critical
|
HL7 message skipped due to an error\={0}
Cause:
Action:
|
