Messages in the continuous queue are not processed

Resolving The Problem

The MDBs in the ejb-jar.xml and ibm-ejb-jar-bnd.xmi will need to be uncommented.

Look for the following sections in the ejb-jar.xml and ensure the MDBs for both the continuous and continuous error queues are uncommented as in the following example:

<!-- MEA MDB -->

<message-driven id="MessageDriven_JMSContQueueProcessor_1">
<ejb-name>JMSContQueueProcessor-1</ejb-name>
<ejb-class>psdi.iface.jms.JMSContQueueProcessor</ejb-class>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<env-entry>
<env-entry-name>MESSAGEPROCESSOR</env-entry-name>
<env-entry-type>java.lang.String </env-entry-type>
<env-entry-value>psdi.iface.jms.QueueToMaximoProcessor</env-entry-value>
</env-entry>
</message-driven>


<!-- MEA MDB for error queue -->

<message-driven id="MessageDriven_JMSContQueueProcessor_2">
<ejb-name>JMSContQueueProcessor-2</ejb-name>
<ejb-class>psdi.iface.jms.JMSContQueueProcessor</ejb-class>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<env-entry>
<env-entry-name>MESSAGEPROCESSOR</env-entry-name>
<env-entry-type>java.lang.String </env-entry-type>
<env-entry-value>psdi.iface.jms.QueueToMaximoProcessor</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>MDBDELAY</env-entry-name>
<env-entry-type>java.lang.Long </env-entry-type>
<env-entry-value>30000</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>ERRORQUEUE</env-entry-name>
<env-entry-type>java.lang.String </env-entry-type>
<env-entry-value>1</env-entry-value>
</env-entry>

</message-driven>



At the bottom of the file, ensure the following are also uncommented as in the following:



<!-- MEA MDB -->

<container-transaction>
<method>
<ejb-name>JMSContQueueProcessor-1</ejb-name>
<method-name>*</method-name>
</method>

<trans-attribute>Required</trans-attribute>

</container-transaction>
<!-- MEA MDB for error queue -->

<container-transaction>
<method>
<ejb-name>JMSContQueueProcessor-2</ejb-name>
<method-name>*</method-name>
</method>

<trans-attribute>Required</trans-attribute>

</container-transaction>


Now look for the sections in the ibm-ejb-jar-bnd.xmi file to ensure the MDBs are also uncommented as in the following example:

<!-- MEA MDB -->
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_1" activationSpecJndiName="intjmsact">
<enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_1"/>
</ejbBindings>
<!-- MEA MDB for error queue -->
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_1" activationSpecJndiName="intjmsacterr">
<enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_2"/>
</ejbBindings>


Once all sections have been uncommented, rebuild and redeploy your maximo.ear. When the application server starts, the MDBs will be activated on the continuous queues and messages will then be delivered to Maximo.