|
|
|
JMSBC-W0502 |
Warning |
Failed to close the file-based
connection information persister with directory {0} and filename {1}: {2}. Cause: An IOException or IO
error occurred while writing the connection properties file. Action: If this problem occurs consistently,
contact Oracle for support. |
JMSBC-W0703 |
warning |
Failed to initiate XA recovery; recovery will be attempted
again the next time the component will be initialized (init): {0}. Cause: The MQ
Broker might not be running. Action: If this problem occurs consistently, contact Oracle for
support. |
JMSBC-W0205 |
warning |
Failed to delete temporary {0} with name {1}: {2}. Cause: A JMS Exception
is thrown if it is still in use by existing subscribers. Action: No
action required. |
JMSBC-E0757 |
critical |
Failed to prepare the channel(s) for endpoint {0} of service {1}. Cause: MQ
Broker might not be running. Action: Check to see if the MQBroker is running, or
check that the connection parameters are correct. |
JMSBC-E0726 |
critical |
Failed to deploy the service unit
{0} from service unit path {1}: {2}. Cause: There could be various reasons why a
service unit is not deployed. In most cases this occurs because the JBI
runtime is not able to deploy. Action: Check the server log for details and
take corrective action based on the same. |
JMSBC-E0731 |
critical |
The JMS message property {0} is
of an unknown type {1}. Cause: The JMS message property may contain an invalid
value. The correct types are Boolean, short, int, long, float, double, and String.
Action: Ensure that the JMS message contains a valid value. |
JMSBC-W0720 |
warning |
Some other thread is
running the shutdown for endpoint {0} Cause: The current thread checks the state of
a given endpoint. An exception is thrown if another thread has already initiated
the shutdown. Action: No action required. |
JMSBC-W0206 |
warning |
Failed to close MessageConsumer which is receiving on
temporary {0} with name {1}: {2}. Cause: An internal has prevented the JMS provider to
close the consumer. Action: Check the MQ Broker log corresponding to this event
for more information. |
JMSBC-W0724 |
warning |
Failed to retrieve QOS from service unit root path {0}. Cause:
A QOS Configuration property contains an incorrect value. Action: If this problem occurs consistently, contact
Oracle for support. |
JMSBC-W0708 |
warning |
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}. Cause: In most cases this is due to
invalid WSDL binding. Action: Rectify the WSDL binding with the correct message part. |
JMSBC-W0716 |
warning |
Error
occurred while deactivating endpoint {0} of service {1} for service unit {2}: {3} Cause:
JBI runtime is not able to deactivate an endpoint. Action: If this problem
occurs consistently, contact Oracle for support. |
JMSBC-W0732 |
warning |
Suspended endpoint {0}. Cause: An endpoint has been suspended by
admin or a user using JMX. Action: Restart the endpoint. |
JMSBC-W0730 |
warning |
Unable to denormalize
reply from internal service engine/binding component for message exchange {0}, end point {1}
and operation {2}. Cause: An invalid normalized message which came as response from the
partner component. Action: Check the response or normalized message. |
JMSBC-W0709 |
warning |
The message part {0} did not
get added as JMS TextMessage text; there is no such WSDL message part
with the name {0}. Cause: An invalid WSDL binding. Action: Make sure the message part
exists as specified in the binding section. |
JMSBC-W0501 |
warning |
Found an unexpected connection value {0}
in a connection record in directory {1}, filename {2}. Cause: Persisted connection info/record has invalid
parameters. Action: If this problem occurs consistently, contact Oracle for support. |
JMSBC-E0309 |
critical |
Failed to load application
configuration from {0} got error {1}. Cause: Unable to read the persisted file. Action: If
this problem occurs consistently, contact Oracle for support. |
JMSBC-E0761 |
critical |
Transaction rollback failed for transaction {0}
, endpoint {1} of service {2}. The current status of transaction is {4}. Cause:
The transaction manager encountered an unexpected error condition. Action: If this problem occurs consistently, contact
Oracle for support. |
JMSBC-E0714 |
critical |
Failed to set the {0} property to true on the
JMS message Plugin insertion failed: Could not find plugin 1: {2}. Cause: Might be
due to jmsjca internal errors. Action: If this problem occurs consistently, contact Oracle for support. |
JMSBC-E0762 |
critical |
Could
not register management MBean for component {0}. Cause: Check the JMX documentation for MBeanServer.registerMBean. Action:
Take appropriate action based on the server log. |
JMSBC-W0002 |
warning |
Found an unexpected attribute {0} for
element {1} in service definition {2}; this attribute will be ignored. Cause: Invalid attribute in
the WSDL service definition. Action: Check the WSDL. |
JMSBC-E0308 |
critical |
Failed to load application variable {0}
got error {1}. Cause: Unable to Load the persisted configuration. Action: If this problem occurs consistently,
contact Oracle for support. |
JMSBC-W0710 |
warning |
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. Cause: May be caused by a invalid normalized message. Action: Increase logging verbosity and check
to ensure that the normalized message is valid. |
JMSBC-E0752 |
critical |
Received the following error on
the message exchange with ID {0} and pattern {1}: {2}. Cause: May be caused
by an internal error or partner component error. Action: If this problem occurs consistently, contact
Oracle for support. |
JMSBC-E0708 |
critical |
Failed to commit XA transaction Plugin insertion failed: Could not find
plugin 0: {1}. Cause: A transaction rolled back or a transaction manager error occurred. Action:
If this problem occurs consistently, contact Oracle for support. |
JMSBC-W0717 |
warning |
Error occurred while removing channel(s)
for endpoint {0} of service {1} for service unit {2}: {3}. Cause: A error
occurred while closing the connection to the JMS Server. Action: Check the GlassFish and
JMS Server log for more details. |
JMSBC-W0102 |
warning |
Failed to find a matching ManagedConnectionFactory with
connectionURL {0}, merged options {1}. Cause: The managed connection factory may already be released. Action: If
this problem occurs consistently, contact Oracle for support. |
JMSBC-W0728 |
warning |
Unable to send message to JMS
provider, message exchange {0}, end point {1} and operation {2}. Cause: The JMS Server
may be down. Action: If this problem occurs consistently, contact Oracle for support. |
JMSBC-W0504 |
warning |
Failed to register
XAResource (registerXAResource) to connection {0} for transaction recovery; will try again on next
JMS Binding Component initialization Cause: The JBI component context could not register the XA Resource
. Action: If this problem occurs consistently, contact Oracle for support. |
JMSBC-W0101 |
warning |
Failed to find a
matching ResourceAdapter with connectionURL {0}, merged options {1}. Cause: The Resource Adapter may be already
released. Action: If this problem occurs consistently, contact Oracle for support. |
JMSBC-W0712 |
warning |
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}. Cause:
The transaction manager encountered an unexpected error condition. Action: If this problem occurs consistently, contact
Oracle for support. |
JMSBC-W0715 |
warning |
The service unit {0} does not contain any WSDL(s) for
which the JMS Binding Component is responsible Cause: No corresponding JMS WSDL is found based
on the endpoint definition . Action: Recreate the application, If this problem occurs consistently,
contact Oracle for support. |
JMSBC-W0704 |
warning |
Failed to parse the component JBI descriptor {0}; component identity
information (version, build number, etc.) is not be available: {1}. Cause: The installer JAR might
not have the required information. Action: If this problem occurs consistently, contact Oracle for
support. |
JMSBC-W0204 |
warning |
Timed out waiting for JMS reply message on temporary {0} with name {1}
after {2} milliseconds. Cause: The application responsible for sending the reply has not replied
within the specified time. Action: Modify the timeout period or make sure the
reply is sent within the specified time. |
JMSBC-E0728 |
critical |
Failed to start the service unit
{0}: {1}. Cause: There could be various reason, such as a duplicate endpoint or
invalid artifacts. Action: Check the server log and take corrective action. If this problem
occurs consistently, contact Oracle for support. |
JMSBC-E0743 |
critical |
An error occurred while attempting to receive a
message exchange from the delivery channel or while processing a message exchange: {0}. Cause: An
error occurred. Check the server log for more information. Action: Check the server log for
details. If this problem occurs consistently, contact Oracle for support. |
JMSBC-E0709 |
critical |
Failed to rollback XA
transaction Plugin insertion failed: Could not find plugin 0: {1}. Cause: The transaction manager encountered
an unexpected error condition. Action: If this problem occurs consistently, contact Oracle for support. |
JMSBC-W0733 |
warning |
Resumed
endpoint {0}. Cause: Endpoint is being resumed by the admin tool or JMX. Action: No
action required. |
JMSBC-E0727 |
critical |
Failed to shut down the service unit {0}: {1}. Cause: An internal
error occurred. Check the server log for more information. Action: Check the server log for
details. If this problem occurs consistently, contact Oracle for support. |
JMSBC-W0706 |
warning |
The content of message
part {0} is null for the WSDL message {1}. Cause: Invalid normalized message. Action: Increase logging verbosity
to see the normalized message, and take corrective action. |
JMSBC-W0719 |
warning |
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}. Cause: Cannot write the information into the persistent store. Action: If this problem
occurs consistently, contact Oracle for support. |
JMSBC-W0701 |
warning |
Failed to close the JMS Message reply sender:
{0}. Cause: Failed to close the JMS sender channel. Action: Check the server log and
the JMS server log, If this problem occurs consistently, contact Oracle for support. |
JMSBC-E0730 |
critical |
The
JMS message property {0} is of an unsupported type {1}. Cause: The JMS
message property contains an invalid type. The correct values are Boolean, short, int, long,
float, double, and String. Action: Ensure that the JMS message configuration property value is
a valid type. |
JMSBC-E0764 |
critical |
Could not suspend endpoint {0}. Cause: Not able to stop all channels
for the endpoint. Action: Check the server log, If this problem occurs consistently, contact
Oracle for support. |
JMSBC-E0749 |
critical |
Failed to send the message exchange with ID {0} and
pattern {1} on the delivery channel due to error: {2}. Cause: Might be due
to some internal error. Action: If this problem occurs consistently, contact Oracle for support. |
JMSBC-E0713 |
critical |
Failed to
process JMS message Plugin insertion failed: Could not find plugin 0 in onMessage:
{1}. Cause: An error occurred. Check the server log for more information. Action: Check the
server log, and take corrective action , If this problem occurs consistently, contact Oracle
for support. |
JMSBC-E0729 |
critical |
Failed to stop the service unit {0}: {1}. Cause: An error occurred. Check
the server log for more information. Action: Check the server log for details. If
this problem occurs consistently, contact Oracle for support. |
JMSBC-W0201 |
warning |
Timed out waiting for dispatched threads
to complete after {0} seconds, connection is {1}, destination is {2}. Cause: The work
manager is unable to shutdown. Some of the worker threads might not have
completed operation within the specified time. Action: If this problem occurs consistently, contact Oracle for
support. |
JMSBC-I0701 |
info |
Unsupported onfailure option {0}. Only "suspend" and "error" can be applied for (IN-OUT
message exchange) service {1} , endpoint {2} and operation {3}. Cause: Invalid QOS property configuration.
Action: Check the server log and rectify the QOS property configuration. |
JMSBC-E0707 |
critical |
Failed to
set rollback XA transaction Plugin insertion failed: Could not find plugin 0: {1}. Cause:
The transaction manager encountered an unexpected error condition. Action: If this problem occurs consistently, contact
Oracle for support. |
JMSBC-E0747 |
critical |
Failed to process the message exchange with ID {0} and
exchange pattern {1} due to error: {2}. Cause: An error occurred. Check the server log
for more information. Action: Check the server log and take corrective action. |
JMSBC-E0755 |
critical |
Failed to stop
endpoint {0} of service {1} for service unit {2}: {3}. Cause: An error occurred. Check
the server log for more information. Action: Check the server log for details. If
this problem occurs consistently, contact Oracle for support. |
JMSBC-E0318 |
critical |
Failed to persist application configuration {0}
got error {1}. Cause: Not able to persist configuration info in the persistent store. Action:
Check the server log for details. If this problem occurs consistently, contact Oracle for
support. |
JMSBC-E0721 |
critical |
Failed to register status MBean for component {0}. Cause: An error occurred with MBeanServer.registerMBean. Action:
Check the JMX documentation for MBeanServer.registerMBean. Take appropriate action based on the server log. |
JMSBC-W0503 |
warning |
Recovery
of transactions is not supported by the JBI runtime in which the JMS
Binding Component is running. Cause: Transaction recovery is not supported by the JBI runtime. Action:
If this problem occurs consistently, contact Oracle for support. |
JMSBC-W0001 |
warning |
Found an environment variable {0}
for attribute {1} in service definition {2} but there is no value assigned
for it; it will be ignored. Cause: Undefined environment variable. Action: Check the server log and
take corrective action. |
JMSBC-W0707 |
warning |
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. Cause: Invalid WSDL
binding or no correspond message part. Action: Check the WSDL. |
JMSBC-W0718 |
warning |
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}. Cause: The JMS
server might not be running. Action: Check the server log and take corrective action. |
JMSBC-W0727 |
warning |
Unable to
process message exchange {0}, end point {1} and operation {2}. Cause: Unable to process the
message exchange from the partner. Action: Check the server log and take corrective action. |
JMSBC-W0203 |
warning |
Failed
to close connection to {0}: {1}. Cause: The JMS provider failed to close the
connection due to some internal error. For example, a failure to release resources
or to close a socket connection. Action: Check the server log for details. If
this problem occurs consistently, contact Oracle for support. |
JMSBC-W0731 |
warning |
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. Cause: Invalid message format send by the client. Action: Check the server log and
rectify. |
JMSBC-E0701 |
critical |
Failed to create a MessageEndpoint. Cause: Failed to create an inbound JMS message endpoint. Action:
Check the server log for details and take corrective action. |
JMSBC-W0705 |
warning |
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} Cause: The component installer might be invalid.
Action: contact Oracle for support |
JMSBC-W0721 |
warning |
Waited long enough for in process messages to complete.
Shutting down the endpoint {0} Cause: An endpoint has been shutdown before it has completely
processed a message. Action: If this problem occurs consistently, contact Oracle for support. |
JMSBC-E0748 |
critical |
Failed to
set the status on the message exchange with ID {0} and pattern {1}
due to error: {2} Cause: Invalid state transition of the message exchange. Action: If this
problem occurs consistently, contact Oracle for support. |
JMSBC-E0772 |
critical |
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. Cause: Not able to normalize the JMS message. Action:
Check that the message is valid based on the WSDL binding, the message
parts, and the properties. |
JMSBC-E0317 |
critical |
Failed to persist application variable {0} got error {1} Cause:
Not able to persist configuration information in the persistent store. Action: Check the server log
for details. If this problem occurs consistently, contact Oracle for support. |
JMSBC-W0505 |
warning |
Failed to determine
whether transaction recovery is supported by the JBI runtime due to error: {0} Cause:
The JBI runtime does not support transaction recovery. Action: Contact Oracle support. |
JMSBC-E0725 |
critical |
Failed to initialize
the service unit {0} from service unit path {1}: {2}. Cause: Various reasons, such as
duplicate endpoints or invalid artifacts. Action: Check the server log for details and
take corrective action. |
JMSBC-E0750 |
critical |
Failed in reply listener while processing message exchange with ID {0}
and exchange pattern {1} due to error: {2} Cause: Message acknowledgement failed or the
endpoint is already shutdown. Action: Check the server log for details. If this
problem occurs consistently, contact Oracle for support. |