Hi Ajith,

It seems the configs are not correct in the sample, Also in your second
step the parameter name is *<parameter
name="max.delivery.attempts">4</parameter> *which is correct, but in the
sample the Property is given *<parameter
name="max.deliver.attempts">50</parameter>. *This must be causing the
inconsistent behavior.

With Regards,

On Wed, Oct 7, 2015 at 8:27 AM, Ajith Vitharana <aji...@wso2.com> wrote:

> Hi All,
>
> I updated source view from the configuration mentioned in sample [1].
>
> i) When I double check the message processor configs from source view, I
>  noticed same config as the sample (expected behavior).
>
>     <messageProcessor
> class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
> messageStore="*pending_subscriptions*" name="send_pending_message"
> targetEndpoint="DurableSubscriberEndpoint">
>         <parameter name="interval">1000</parameter>
>         <parameter name="throttle">false</parameter>
>         <parameter
> name="target.endpoint">DurableSubscriberEndpoint</parameter>
>     *    <parameter name="max.deliver.attempts">50</parameter>*
>     </messageProcessor>
>
> ii) When I go to the "Message Processors" UI and edit the config (wrong
> configurations)
>
> <messageProcessor name="send_pending_message"
> class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
> targetEndpoint="DurableSubscriberEndpoint" messageStore="
> *pending_subscriptions*" xmlns="http://ws.apache.org/ns/synapse";>
>    <parameter name="interval">1000</parameter>
>    <parameter name="client.retry.interval">1000</parameter>
>   * <parameter name="max.delivery.attempts">4</parameter>*
>    <parameter name="is.active">true</parameter>
>    <parameter name="max.delivery.drop">Disabled</parameter>
>    <parameter name="member.count">1</parameter>
> </messageProcessor>
>
> iii) According to the sample ,  I noticed  the message processor is
> deactivating after the 4 attempts, that means the second config executing
> at mediation.
>
>
> iv) When I check the file in synapse-configs/default/message-processors
> that is updated with my new configs.
>
> <?xml version="1.0" encoding="UTF-8"?>
> <messageProcessor xmlns="http://ws.apache.org/ns/synapse";
>
> class="org.apache.synapse.message.processor.impl.forwarder.ScheduledMessageForwardingProcessor"
>                   name="*send_pending_message*"
>                   targetEndpoint="DurableSubscriberEndpoint"
>                   messageStore="pending_subscriptions">
>    <parameter name="interval">1000</parameter>
>    <parameter name="throttle">false</parameter>
>    <parameter name="target.endpoint">DurableSubscriberEndpoint</parameter>
>   * <parameter name="max.deliver.attempts">50</parameter>*
> </messageProcessor>
>
>
> [1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
>
> --
> Ajith Vitharana.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog    : http://vitharana.org
> Mobile : +1-812-360-5335
>
>


-- 
Yasassri Ratnayake
Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
<http://yasassriratnayake.blogspot.com/>*
*            http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>*
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to