How to avoid retries when an async BPEL process fails
We have a BPEL process which, when it throws a rollback exception, sleeps for 10 minutes and then retries again - twice. We want to disable that retry functionality. In other words, once it fails, it fails; don't retry.
Our BPEL kicks off when it receives a message from a JMS queue. After it does its work and builds a response payload, it sends that response to a different JMS queue. After it sends the message to the response queue, it evaluates the XML payload for our custom business fault that may (or may not) have occurred in the BPEL process before the response was sent.