1 Reply Latest reply on Nov 30, 2011 10:00 AM by 902906

    Do we need to stop BPEL process de-hydrating to maintain a global transacti


      We are seeing behaviour where a BPEL process is firing a webservice repeatedly. The webservice it is firing is rolling back. In this case we want the BPEL process to rollback as well. What I think is happening is the BPEL process has dehydrated due to hitting a wait activity and this has broken the global transaction. The BPEL keeps waking up and re-running the service.

      Firstly, does it make sense that the BPEL dehydration is what is causing the repeated re-submission of the service?
      Secondly, can anyone point to documentation explaining what needs to be done to prevent the BPEL from dehydrating?