6 Replies Latest reply on Sep 24, 2013 2:50 PM by oracleistheway

    Disadvantages of setting sync.cache in oneWayDeliveryPolicy


      Hi everyone.


      Currently I have a BPEL set to async.persist, which is not rolling back a transaction as I Catch All a DB fault, store the message, then terminate the process. In one test, I did throw a rollback from the Catch All. This did roll back the transaction but it keeps the Instance state as "Running". Since at that point of manually throwing a rollback I am out of the Catch All, placing a Terminate activity after throwing the rollback doesn't work. I then changed my oneWayDeliverPolicy to sync.cache which did not commit any data to the database if a fault occurred.


      What are some of the disadvantages of using sync.cache?