My Oracle Support Banner

Proxy BS does not throw error on for one-way web service, when target is not reachable (e.g HTTP 400, 401 etc) (Doc ID 1330116.1)

Last updated on MARCH 01, 2018

Applies to:

Siebel CRM - Version 8.0 SIA [20405] and later
Information in this document applies to any platform.


Environment :-
Siebel version :-

Issue :-
When an HTTP 4XX (401 etc) error is returned from the external system, the proxy BS does not raise any error. This was observed in the context of a one-way Web service (outbound case).

Expected Behavior :-
Per Siebel Bookshelf (EAI Volume 2) > Web Services > About One-Way Operations and Web Services :  About One-Way Operations and Web Services :-

Specification R2715. An instance must not consider transmission of one-way operations complete until a HTTP response status code of either 200 OK or 202 Accepted is received by the HTTP client.

Therefore, when an HTTP status code other than 200, 202 is returned, and the workflow invoking the proxy BS ends in a 'Stop' step,  the workflow should raise an exception and move to the 'Stop'.

Actual Behavior :-
The workflow moves to the next step and continues normally instead of following the exception branch to the 'Stop' step.

Business Impact :-
For one-way web service, this is leading to false assumption that the one way transmission is completed when it is not.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.