Error 404 Testing ORDS REST Service with APEX (Doc ID 2333232.1)

Last updated on AUGUST 04, 2018

Applies to:

Symptoms

ORDS and APEX have been configured, and APEX is running successfully. However, an HTTP 404 error is thrown when making an APEX based REST request: 
http://<IP ADDRESS>:8080/ords/rrhh/hr/empinfo/

The error appearing in the Tomcat log (catalina.out) shows the following:

Nov 27, 2017 5:15:58 PM
WARNING: *** jdbc.MaxLimit in configuration |apex|al| is using a value of 10, this setting may not be sized adequately for a production environment ***
Nov 27, 2017 5:15:58 PM
WARNING: *** jdbc.InitialLimit in configuration |apex|al| is using a value of 3, this setting may not be sized adequately for a production environment ***
Nov 27, 2017 5:15:58 PM oracle.ucp.common.UniversalConnectionPoolBase initInactiveConnectionTimeoutTimer
INFO: inactive connection timeout timer scheduled
Nov 27, 2017 5:15:58 PM oracle.ucp.common.UniversalConnectionPoolBase initInactiveConnectionTimeoutTimer
INFO: inactive connection timeout timer scheduled
Nov 27, 2017 5:15:58 PM
SEVERE: *** The pool named: |apex|pu| is reporting no APEX workspaces are enabled for RESTful Services,
but the pool named: |apex|al| is reporting 4 workspaces are enabled.
This implies APEX was installed after Oracle REST Data Services. Please run the following command and restart Oracle REST Data Services:
java -jar ords.war validate --database apex
APEX based RESTful Services, including those used to serve static resources will not function until this has been done.
***

What is causing this failure?

Changes

 Using APEX based REST services with ORDS.

Cause