Oracle JDBC (MOSC)

MOSC Banner

Universal Connection Pool shutdown before app when pod is killed

in Oracle JDBC (MOSC) 7 commentsAnswered ✓

When our kubernetes pods are taken down the UCP is shutdown immediately, even before requests has stopped coming in to the app. Running a spring boot we keep the app up 10 seconds since the pod can get requests even after the sig kill signal. But that does not help much since the database is not responsive.

Is it possible to have a graceful shutdown somehow?

Using the Oracle UCP 21.5.0.0.

Trying to use the DB after sig kill signal results in the following stacktrace:
oracle.ucp.UniversalConnectionPoolException: Universal Connection Pool is about to shutdown: low chance to get a connection at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:379)

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center