Issue in maxRedelivery for Websphere MQ

[Richard Swart]

Hi,

From my mule client 2.2.1, I'm trying to send Messages to a queue in MQ. In normal scenarios it works fine.
But if there is any network issue, mule will not be able to send message to the MQ. I've used the 'maxRedelivery'
for keep resending the message. But its not redelivering the message even the network connection is restored
immediately.

Following is my config file:

<jms:connector
        name="jmsConnector"
        specification="1.1"
        connectionFactory-ref="mQfactory" username="abc" password="" disableTemporaryReplyToDestinations="true"
        maxRedelivery="1000" numberOfConcurrentTransactedReceivers="1"/>

<spring:beans>
         <spring:bean id="mQfactory" class="com.ibm.mq.jms.MQConnectionFactory">
             <spring:property name="hostName" value="${hostName}"/>
             <spring:property name="port" value="${port}"/>
             <spring:property name="transportType" value="${transportType}"/>
             <spring:property name="queueManager" value="${queueManager}"/>
             <spring:property name="rescanInterval" value="2000"/>
         </spring:bean>
</spring:beans>

Could someone explain how the redelivery works. Any help on this regard is much appreciated.

Thanks
Vaithi


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Andrew Perepelytsya]

Max redelivery is for inbound. It's delivery count from provider to listener (Mule).

HTH,
Andrew

On Jun 25, 2009 3:14 AM, "vaithi m" <mule.user.relay@...> wrote:

Hi,

From my mule client 2.2.1, I'm trying to send Messages to a queue in MQ. In normal scenarios it works fine.
But if there is any network issue, mule will not be able to send message to the MQ. I've used the 'maxRedelivery'
for keep resending the message. But its not redelivering the message even the network connection is restored
immediately.

Following is my config file:

&lt;jms:connector
       name="jmsConnector"
       specification="1.1"
       connectionFactory-ref="mQfactory" username="abc" password="" disableTemporaryReplyToDestinations="true"
       maxRedelivery="1000" numberOfConcurrentTransactedReceivers="1"/&gt;

&lt;spring:beans&gt;
        &lt;spring:bean id="mQfactory" class="com.ibm.mq.jms.MQConnectionFactory"&gt;
            &lt;spring:property name="hostName" value="${hostName}"/&gt;
            &lt;spring:property name="port" value="${port}"/&gt;
            &lt;spring:property name="transportType" value="${transportType}"/&gt;
            &lt;spring:property name="queueManager" value="${queueManager}"/&gt;
            &lt;spring:property name="rescanInterval" value="2000"/&gt;
        &lt;/spring:bean&gt;
&lt;/spring:beans&gt;

Could someone explain how the redelivery works. Any help on this regard is much appreciated.

Thanks
Vaithi


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Richard Swart]

Thanks Andrew. I've had a wrong perception on that.

But could you please give a hint on how to resend the failed message to MQ for a given number of times?


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[antoine.borg]

Have you looked at retry policies?
http://www.mulesource.org/display/MULE2USER/Configuring+Retry+Policies

Depends on what constitutes a failure, perhaps.

HTH

A

vaithi m wrote:

> Thanks Andrew. I've had a wrong perception on that.
>
> But could you please give a hint on how to resend the failed message to MQ for a given number of times?
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>
>  

--

Antoine Borg, Senior Consultant | Tel: [phone]
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM

See our full schedule of Mule and Android courses:
http://www.ricston.com/courses/schedules/

email: _antoine.borg_@... <mailto:antoine.borg@...> |
blog: blog.ricston.com <http://blog.ricston.com> | web: ricston.com
<http://www.ricston.com/>



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Richard Swart]

Antony, thanks for the reply.

I've also configured the Custom retry policies. But it is getting called only for the inbound JMS messages.
If an outbound message fails, it doesnt seems to be retrying.

Is that the correct behaviour?

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[antoine.borg]

What failure are you seeing? Do you have some exception logs we can look at?

A

vaithi m wrote:

> Antony, thanks for the reply.
>
> I've also configured the Custom retry policies. But it is getting called only for the inbound JMS messages.
> If an outbound message fails, it doesnt seems to be retrying.
>
> Is that the correct behaviour?
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>
>  

--

Antoine Borg, Senior Consultant | Tel: [phone]
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM

See our full schedule of Mule and Android courses:
http://www.ricston.com/courses/schedules/

email: _antoine.borg_@... <mailto:antoine.borg@...> |
blog: blog.ricston.com <http://blog.ricston.com> | web: ricston.com
<http://www.ricston.com/>



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email