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?
I see some confusion here.
1. you mentioned BPEL process is will be firing WS repeatedly
2. WS invoked rollback hence your BPEL process should/will rollback
3. Wait acitivity used is causing dehydration.
4. Resubmission is happening ?(Refere 1, 2 again this will answer your doubt)
5.You do not want dehydration ? (Refer 3.)