ExpiryQueue for MQQueue MDB

[sven.loe]

Hello,

I have connected 3 MQQueues to 3 MDBs on JBoss. The config is working but I need a separate ExpiryQueue for each of the MQQueues. If processing a message failes the message must be copied to their expiryQueue for further processing. The config seems not to offer such a feature. Does somebody know how to configure an ExpiryQueue per MQQueue? The rar is from WS 6.1. The config is:

<server>

    <!-- mbeans defining JCA administered objects -->

    <mbean code="org.jboss.resource.deployment.AdminObject"

        name="jboss.jca:service=WASDestination,name=elanContractFlowDeltaJca">

        <!-- this MBean depends on the WebSphere MQ resource adapter -->

        <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'

        </depends>

        <depends>jboss.jca:service=ConnectionFactoryBinding,name=JmsXA</depends>

        <!-- Bind this AdminObject  with the JNDI name wsmq/RequestQueue -->

        <attribute name="JNDIName">jms/rdp/elanContractFlowDeltaQueue

        </attribute>

        <!-- this admin object is a javax.jms.Queue -->

        <attribute name="Type">javax.jms.Queue</attribute>

        <!-- Attribute does not exist

        <attribute name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=jms/rdp/elanContractFlowExceptionQueue</attribute>

         -->

        <attribute name="Properties">

            baseQueueManagerName=QT01

            baseQueueName=A.SERV.QUE

        </attribute>

    </mbean>

<server>

<?xml version='1.0' encoding='UTF-8' ?>

<jboss>

    <enterprise-beans>

        <message-driven>       

            <resource-adapter-name>wmq.jmsra.rar</resource-adapter-name>

            <ejb-name>AdapterMDB</ejb-name>

            <configuration-name>Standard Message Inflow Driven Bean</configuration-name>       

            <activation-config>

                <activation-config-property>

                    <activation-config-property-name>destination

                    </activation-config-property-name>

                    <activation-config-property-value>jms/myQueue

                    </activation-config-property-value>

                </activation-config-property>

                <activation-config-property>

                    <activation-config-property-name>destinationType

                    </activation-config-property-name>

                    <activation-config-property-value>javax.jms.Queue

                    </activation-config-property-value>

                </activation-config-property>

                <activation-config-property>

                    <activation-config-property-name>hostName

                    </activation-config-property-name>

                    <activation-config-property-value>host

                    </activation-config-property-value>

                </activation-config-property>

                <activation-config-property>

                    <activation-config-property-name>port

                    </activation-config-property-name>

                    <activation-config-property-value>1111

                    </activation-config-property-value>

                </activation-config-property>

                <activation-config-property>

                    <activation-config-property-name>channel

                    </activation-config-property-name>

                    <activation-config-property-value>CLIENT.TO.QT01

                    </activation-config-property-value>

                </activation-config-property>

                <activation-config-property>

                    <activation-config-property-name>queueManager

                    </activation-config-property-name>

                    <activation-config-property-value>QT01

                    </activation-config-property-value>

                </activation-config-property>

                <activation-config-property>

                    <activation-config-property-name>transportType

                    </activation-config-property-name>

                    <activation-config-property-value>CLIENT

                    </activation-config-property-value>

                </activation-config-property>

                <activation-config-property>

                    <activation-config-property-name>useJNDI

                    </activation-config-property-name>

                    <activation-config-property-value>true

                    </activation-config-property-value>

                </activation-config-property>

            </activation-config>

        </message-driven>

    </enterprise-beans>

</jboss>

Yours

Sven

[wdfink]

Does http://docs.jboss.org/jbossmessaging/docs/usermanual-2.0.0.beta1/html/message-expiry.html helps.

You might configure this for each queue.

[sven.loe]

The Problem is that

<mbean code="org.jboss.resource.deployment.AdminObject" name="jboss.jca:service=WASDestination,name=elanContractFlowDeltaJca">

is not a JBoss queue and it has no DLQ, ExpiryQueue attributes. The question is can the JBoss container handle exceptions thrown while processing the messages of IBM MQQueues or has the host to do it?