503 Error When Using Oauth With ORDS (Doc ID 2636672.1)

Last updated on NOVEMBER 11, 2022

Applies to:

Symptoms

1. Using ORDS 17.4.1.353.06.48.
2. ORDS is running in a two node weblogic cluster Load Balanced by F5.
3. A Restful service is involved in the following:

----1. Payment information is sent to the initial API.
----2. That API puts a message in a queue to be processed.
----3. A message consumer sends the payment information to the vendor.
----4. The vendor results are put into another queue to be processed.
----5. A result consumer picks up the message.
----6. Payment plan information is sent to the database via an ORDS endpoint.
----7. Payment status information is sent to the database via another ORDS endpoint.
----8. Financial posting information is sent to the database via another ORDS endpoint.

The 503 error occurs on 6 and 7, depending on which is hit first.

Steps 1-5 are not using ORDS

Note: Developers handle the 503 exception which involves retrying and on the retry the 503 does not occur again.

4. Using two legged OAuth2.0

5. No pattern to this. Can be reproduced in Standalone ORDS. Does not seem to be load related but does appear to be intermittent.

6. ords log shows:

Many errors like the following:

WARNING: The connection pool named: apex_pu is not correctly configured, due to the following error(s): Protocol violation: [ 8, 1, ]
oracle.dbtools.common.jdbc.ConnectionPoolConfigurationException: The connection pool named: apex_pu is not correctly configured, due to the following error(s): Protocol violation: [ 8, 1, ]

Caused by: oracle.dbtools.common.ucp.ConnectionLabelingException: Error occurred when attempting to configure url: jdbc:oracle:thin:@//machine:1521/ords_oradev with labels: {oracle.dbtools.jdbc.label.schema=<SCHEMA_NAME>}

==========================================================================================================

WARNING: Error occurred when sending response for:
404 GET https://<HOST>/ords/<SCHEMA_NAME>/oath/token
WARNING: null
org.eclipse.jetty.io.EofException
at org.eclipse.jetty.io.ChannelEndPoint


7.  11.2.0.4 RAC DB
APEX is NOT in the DB
APEX_PUBLIC_USER is in the DB
ORDS 18.3 and schemas are present.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.