We are using the 19.4.6 version of ORDS currently in production and want to move to the latest one 21.2.4.
We are facing to a different behavior when ORDS start and database is not yet ready, the connection is never resumed and stand with the 404 configuration mapping error.
According some reference we don't have to restart ORDS when the database is down.
Does ORDS Require a Restart When the Database Has Been Shutdown and Restarted? (Doc ID 2630478.1)
That's correct but ONLY if the connection was attempt at startup time.
Easy step to reproduce:
1. Set the retry time value in a lowest value for testing only
<entry key="db.invalidPoolTimeout">1m</entry>
2. Shutdown the configured database
3. Start ORDS
4. Invoke one Rest ressource
You will receive a 404 error have in the log : (where xx is the configured pool)
The pool named: |xx|pu| is invalid and will be ignored: ORDS was unable to make a connection to the database. This can occur if the database is unavailable, the maximum number of sessions has been reached or the pool is not correctly configured. The connection pool named: |xx|pu| had the following error(s): ORA-01033: ORACLE initialization or shutdown in progress
5. Start the database
6. Wait 1 or 2 minutes
7. Invoke again one Rest ressource
You still receive the 404 error and never resume.
@thatjeffsmith-oracle, this was already identified on your side ?