My Oracle Support Banner

RESTful Web Service Test Results in 404 Not Found Error When Using ORDS 3.0 (Doc ID 2054141.1)

Last updated on FEBRUARY 18, 2021

Applies to:

Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Trying to test a simple RESTful web service results in 404 Not Found error.

NotFoundException [statusCode=404, reasons=[]]
at oracle.dbtools.url.mapping.URLMappingsProvider.map(URLMappingsProvider.java:79)
at oracle.dbtools.url.mapping.filter.URLMappingFilter.doFilter(URLMappingFilter.java:55)
at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)
at oracle.dbtools.http.locale.LocaleFilter.doFilter(LocaleFilter.java:60)
at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:45)

...

 

For example: Test the RESTful web service oracle.example.hr from SQL Workshop
SQL Workshop -> RESTful Service -> oracle.example.hr -> employees/{id}, select GET -> Test Button

 

Issue reproduces using ORDS 3.0.x and 2.0.5 and higher.

Changes

 Upgraded Apex.

Error does not reproduce in a new workspace created in the upgraded version. It reproduces only in an existing workspace that was created in a pre 4.1 release of APEX.

Cause

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
Symptoms
Changes
Cause
Solution
References


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