Suppose you have a Proxy based Web Service using Oracle Service Bus. In a stage in the request pipeline, 
you are using a Publish action to publish the incoming message to a JMS queue using a Business Service. What if the outbound transport provider throws an exception (outside of your pipeline)? Is your pipeline able to catch the error with an error handler??

This situation could occur because of a faulty connection, suspended queue, or some other reason. Here is the Request Pipeline in our simple test case.

With an Error Handler added to the message flow containing a simple Log action.

By default, the Publish action will invoke the service in a fire and forget fashion. Therefore any exception that occurs in the outbound transport will go unnoticed as shown in the following Invocation Trace.

So what now? In a message flow, you can apply a Routing Options action to modify any or all of the following properties in the outbound request: URI, Quality of Service, Mode, Retry parameters, Message Priority.

Now add the Routing Options action to the Request Action as shown below.

Click the Routing Options to display its properties in the Properties View. Select the QoS option to set the Quality of Service element. Select Exactly Once to override the default setting, and Republish the project. The invocation will now block until the message is completely processed.

Trying the same test case as earlier generates the following Invocation Trace showing that the Error Handler is now triggered.