500 Internal Server Error : When Using ORDS 3.x and URL Mapping
(Doc ID 2060089.1)
Last updated on FEBRUARY 09, 2023
Applies to:
Oracle Application Express (APEX) - Version 4.2 and laterOracle REST Data Services - Version 3.0.1 to 3.0.1 [Release APEX 3.0]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Oracle REST Data Services (ORDS) has been set up to have an additional database connect using the URL Mapping feature. In trying to access the new URL Mapping, an "500 Internal Server Error" is given as shown in the following screenshot.
Furthermore, if ORDS is running standalone, then the following exception can be seen in the console window that started ORDS.
Depending on which URL was accessed first, you could see the above Internal Server Error or a Spinning Browser wheel. That is, if the default APEX URL was accessed, then the Internal Server Error is shown. If after this you access the new mapped URL, you would see a browser with a spinning wheel.
Changes
ORDS has been configured to have an additional database via URL Mapping as per the documentation.
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 |