Problems in deploying MDBs

 

Failures might occur when the application server attempts to start message delivery to an MDB. This kind of failure is typically caused by an error in the definition of the associated ActivationSpec object, or because the resources referenced in the definition are not available. For example, the queue manager might not be running, or a specified queue might not exist.

An ActivationSpec object attempts to validate its properties when the MDB is deployed, and deployment fails if the ActivationSpec object has any properties that are mutually exclusive or does not have all the required properties. However, not all problems associated with the properties of the ActivationSpec object can be detected at this time.

Deployment might also fail if an MDB is transacted and the connection is in client mode, but distributed transactions are not available because the extended transactional client JAR file, com.ibm.mqetclient.jar, is not in the class path.

Failures to start message delivery are reported to the user in a manner that depends on the application server. Typically, these failures are reported in the logs and diagnostic trace of the application server. If enabled, the diagnostic trace of the WebSphere MQ resource adapter also records these failures.

uj40170_