I’m encountering an ORDS/REST issue on apex.oracle.com that appears to be related to database connection pooling or proxy authorization, and I’m hoping for guidance or confirmation that this is a platform-side issue.
Environment
- Oracle APEX hosted service: apex.oracle.com
- APEX version: (current hosted version)
- Workspace schema:
WKSP_STEPHENWS
- Schema alias in ORDS URL:
stephen_ws
- REST services created via SQL Workshop → RESTful Services
REST Module
- Base Path:
hr
- Resource Template:
employees/:id
- Method:
GET
- Source Type: Query / Collection Query
- SQL Source:
select * from employees where employee_id = :id
The SQL works correctly when run in SQL Workshop → SQL Commands and returns a row for a valid employee_id.
REST URL
https://oracleapex.com/ords/stephen_ws/hr/employees/100
Problem
Calling the REST endpoint directly in a browser results in a 500 error (or the request hangs).
I attempt to call the same REST endpoint from within my web app using APEX_WEB_SERVICE.make_rest_request using the following PL/SQL in a dynamic action:
l_base_url VARCHAR2(200) := 'http://oracleapex.com/ords/stephen_ws/';
l_id := :P304_EMPLOYEE_ID;
l_clob := apex_web_service.make_rest_request(
p_url => l_base_url || 'hr/employees/' || l_id,
p_http_method => 'GET'
);
In the debug output I see the following response:
HTTP response 571
{
"code": "DatabaseConnectionError",
"title": "Database Connection Error",
"message": "The database user for the connection pool named |default|lo|, is not able to proxy to the schema named WKSP_STEPHENWS. This could be a configured restriction on the maximum number of database sessions or an authorization failure.",
"type": "tag:oracle.com,2020:error/DatabaseConnectionError",
"instance": "tag:oracle.com,2020:ecid/ZT_E_FoN6eMzqnlqcDcccA"
}
Additional diagnostics:
- The SQL query works when executed directly in the workspace schema.
- Creating a trivial “ping” REST endpoint (e.g.
select 'OK' from dual) also results in the browser hanging.
- This suggests the issue is not specific to the
employees table or query.
- The error indicates ORDS cannot proxy from its connection pool user into the workspace schema.
Question
Is this a known ORDS connection pool / proxy issue on the hosted APEX service?
If so:
- Is this typically transient (pool/session exhaustion)?
- Or does it require Oracle-side intervention to restore proxy authorization for the schema?
I’ve included the ECID above in case Oracle staff can trace this in the logs.
Thanks in advance for any insight.
Stephen