Hi together, I'm working on a proof-of-concept project and I'm following the store-and-forward-messaging pattern example [1].
There is a question regarding ScheduledMessageForwardingProcessor and it's intended behaviour: Is there a way to dequeue a message stored in the message store (jms queue) in case of an (specific) fault? The idea was to point the ScheduledMessageForwardingProcessor to a custom fault-sequence, and in cases of application errors dequeue the specific message. Although the property "message.processor.fault.sequence" was set and the sequence is called in case of an fault (the log shows up in the console), the message still stays in the message store (queue). This is the snippet of the fault sequence: <sequence xmlns="http://ws.apache.org/ns/synapse"; name="MyFaultSequence"> <log level="full" category="ERROR"> <property name="MSG" value="+++++++++++FAULT+++++++++++++++++++" /> </log> <!-- complex fault handling omitted in this snippet --> <drop /> </sequence> Any help and hints would be appreciated. Thanks, Jochen [1] http://wso2.org/library/articles/2011/12/implementing-store-forward-messaging-patterns-wso2esb-part-2 _______________________________________________ User mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/user
