Connect To Url Filter Does Not Run Fail Policy On Response Time Out (Doc ID 1667561.1)

Last updated on MAY 17, 2016

Applies to:

Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.
A connect to url filter can have an optional "Call policy on failure" set to trigger a policy upon failure, the failure being that the url doesn't exist (server/port not listening) etc.

One scenario where this doesn't work is if the server and port are correct, but the response from the server exceeds the default 30 second timeout within OAG. (I.E. - the destination server has accepted the request from OAG, but takes more than 30 seconds to process it and return a response.)
Currently it simply throws a 500 error and ignores the Policy configured to run on failure. How can we resolve this issue ?

Goal

A connect to url filter can have an optional "Call policy on failure" set to trigger a policy upon failure, the failure being the url doesn't exist (server/port not listening) etc.
One scenario where this doesn't work is if the server and port are correct, but the response from the server exceeds the default 30 second timeout within OAG.  (I.E. - the destination server has accepted the request from OAG, but takes more than 30 seconds to process it and return a response.)
Currently, the system simply throws a 500 error and ignores the Policy configured to run on failure.
 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms