WebSphere MQ resource adapter warning messages

WebSphere MQ resource adapter warning messages

Table 1 describes the WebSphere MQ resource adapter warning messages.

WebSphere MQ resource adapter warning messages
Message ID Message Explanation Action
MQJCA4000 An unknown warning occurred. The resource adapter failed to map an internal reason code to a warning message. This is an internal error.
MQJCA4001 Unknown exception message ID: {0} The exception builder was asked to build an exception but does not understand the requested type. This is an internal error.
MQJCA4002 Failed to find javax.jms.MessageListener class. Inbound messaging unavailable. Check the class path. The javax.jms.MessageListener class was not found in the class path. Inbound messaging is not available, although outbound messaging might still work. A problem with the class path has prevented inbound messaging from starting. Check the class path.
MQJCA4003 A recoverable exception occurred in the JMS layer. See the linked exception for details. A call to a JMS method threw an exception, but this failure does not directly affect the operation of the resource adapter. Investigate the cause of the error. The exception might indicate configuration problems, or more serious issues with the resource adapter or WebSphere MQ queue manager.
MQJCA4004 Message delivery to an MDB failed. See the linked exception for details. An attempt to deliver a message to a Message Endpoint failed. The message has been rolled back onto the queue. We can ignore a single warning if a subsequent attempt to deliver the message is successful. Repeated warnings might indicate problems with the resource adapter or the WebSphere MQ queue manager, or that a corrupt message is on the queue.
MQJCA4005 Distributed transactions are not available in client mode. The extended transactional client JAR file, com.ibm.mqetclient.jar, was not be found in the class path. If the extended transactional client is not required, no action is necessary.
MQJCA4011 An exception was thrown by ManagedConnection.destroy(). An exception was thrown while a managed connection was closing. The error does not affect the operation of the resource adapter because the managed connection was no longer being used. However, the error might indicate configuration problems, or more serious issues with the resource adapter or WebSphere MQ queue manager.
MQJCA4013 A connection to a queue manager failed. Check the queue manager error logs for details. A connection to a WebSphere MQ queue manager was broken. If the reconnectionRetryCount property is not zero, the resource adapter attempts to reconnect to the queue manager. Until the connection is restarted, the delivery of messages to any MDBs supplied by the connection is suspended.
MQJCA4014 Failed to reconnect one or more MDBs after a connection failure. The connection supplying one or more MDBs failed, and the resource adapter was not able to reconnect within the number of attempts specified by the reconnectionRetryCount property. Make sure that the WebSphere MQ queue manager is running, and that any other required components such as a listener are also running. Examine the application server logs to determine which MDBs have failed and restart the MDBs manually.

uj40040_

Message ID	Message	Explanation	Action
MQJCA4000	An unknown warning occurred.	The resource adapter failed to map an internal reason code to a warning message.	This is an internal error.
MQJCA4001	Unknown exception message ID: {0}	The exception builder was asked to build an exception but does not understand the requested type.	This is an internal error.
MQJCA4002	Failed to find javax.jms.MessageListener class. Inbound messaging unavailable. Check the class path.	The javax.jms.MessageListener class was not found in the class path. Inbound messaging is not available, although outbound messaging might still work.	A problem with the class path has prevented inbound messaging from starting. Check the class path.
MQJCA4003	A recoverable exception occurred in the JMS layer. See the linked exception for details.	A call to a JMS method threw an exception, but this failure does not directly affect the operation of the resource adapter.	Investigate the cause of the error. The exception might indicate configuration problems, or more serious issues with the resource adapter or WebSphere MQ queue manager.
MQJCA4004	Message delivery to an MDB failed. See the linked exception for details.	An attempt to deliver a message to a Message Endpoint failed. The message has been rolled back onto the queue.	We can ignore a single warning if a subsequent attempt to deliver the message is successful. Repeated warnings might indicate problems with the resource adapter or the WebSphere MQ queue manager, or that a corrupt message is on the queue.
MQJCA4005	Distributed transactions are not available in client mode.	The extended transactional client JAR file, com.ibm.mqetclient.jar, was not be found in the class path.	If the extended transactional client is not required, no action is necessary.
MQJCA4011	An exception was thrown by ManagedConnection.destroy().	An exception was thrown while a managed connection was closing.	The error does not affect the operation of the resource adapter because the managed connection was no longer being used. However, the error might indicate configuration problems, or more serious issues with the resource adapter or WebSphere MQ queue manager.
MQJCA4013	A connection to a queue manager failed. Check the queue manager error logs for details.	A connection to a WebSphere MQ queue manager was broken.	If the reconnectionRetryCount property is not zero, the resource adapter attempts to reconnect to the queue manager. Until the connection is restarted, the delivery of messages to any MDBs supplied by the connection is suspended.
MQJCA4014	Failed to reconnect one or more MDBs after a connection failure.	The connection supplying one or more MDBs failed, and the resource adapter was not able to reconnect within the number of attempts specified by the reconnectionRetryCount property.	Make sure that the WebSphere MQ queue manager is running, and that any other required components such as a listener are also running. Examine the application server logs to determine which MDBs have failed and restart the MDBs manually.