i consuming message jms queue , submitting soap base web service. want make sure provide guaranteed delivery of message web service submitting message.
i'm looking @ 2 options 1. use until-successful router (preferred) , if unable transmit message put in dead letter queue. 2. use jms transactions, , if transmission of message web service fails rollback transaction , jms message stays in queue.
<jms:inbound-endpoint queue="ws.message"/> <until-successful objectstore-ref="objectstore" dlqendpoint-ref="dlqchannel" maxretries="3" secondsbetweenretries="10"> ... </until-successful>
i more inclined towards using until–successful router concern have requires mandatory objectstore. not want store message in database/object store, instead push jms queue/a dead letter queue , consume there.
any helpful tips or suggestions handle situation appreciated.
if use until-successful, reference objectstore
mandatory. mule uses object store messages between retries. also, should use persistent object store avoid message loss in case of mule server or application crashes. until-successful router should preferred method use case imo. make config easier read , maintain vs using jms queues.
Comments
Post a Comment