synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charith Dhanushka Wickramarachchi (JIRA)" <>
Subject [jira] [Resolved] (SYNAPSE-893) Resequencing Message Processor For Synapse
Date Sat, 01 Jun 2013 22:36:20 GMT


Charith Dhanushka Wickramarachchi resolved SYNAPSE-893.

       Resolution: Implemented
    Fix Version/s: NIGHTLY

Committed the patch. Did some small fixes addressing some typos. Thanks Buddhima for Contribution.
One thing i note is if a message comes to the message store with a smaller sequence number
than current processed out message it will be dropped. As a future improvement we can add
a feature where users can configure an optional sequence to handle this messages. 
> Resequencing Message Processor For Synapse
> ------------------------------------------
>                 Key: SYNAPSE-893
>                 URL:
>             Project: Synapse
>          Issue Type: New Feature
>            Reporter: Buddhima Wijeweera
>            Assignee: Charith Dhanushka Wickramarachchi
>              Labels: patch
>             Fix For: NIGHTLY
>         Attachments: Documentations_&_Sample_703.patch, Documentations_&_Sample_703_v2.patch,
patch.txt, Resequencer.patch, Resequencer.patch, Resequencer.patch
>   Original Estimate: 672h
>  Remaining Estimate: 672h
> Adding Resequencer Message Processor for Synapse.
> Configuration is as follows:
> <messageProcessor 
>             class="org.apache.synapse.message.processors.resequence.ResequencingProcessor"

>             name="ResequencingProcessor" messageStore="MyQueue"> 
> <parameter name="interval">10000</parameter>
> <parameter name="seqNumXpath" xmlns:bank="" expression="//bank:display/bank:seqNo"/>
> <parameter name="nextEsbSequence">next_seq</parameter> 
> <parameter name="requiredInitMessages">15</parameter> 
> <parameter name="requiredInitMessagesDelay">2</parameter>
> <parameter name="deleteDuplicateMessages">true</parameter> 
> </messageProcessor>

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message