The comments section in ENTMQBR-4352 discusses the need to document some opinionated JDBC connection pooling configurations for supported databases.

I've created this issue to track any further discussion/work on that. ENTMQBR-4352 was intended to track the initial work of adding basic documentation for the new configuration options. That is now done, and ENTMQBR-4352 has been closed.

******

Currently, when the AMQ broker looses the connection to the database, it immediately shuts down.

This is a request raised to support a reconnect feature such that the broker should try to reconnect to the database instead of shutting down,

This request is also raised in the context of

if the broker is configured with JDBC persistence using Oracle in HA mode (JDBC Persistence - Oracle Data guard in Grid deployment) .

The expectation is that When Primary Database goes down, broker should switch over to Secondary database.

However the broker instance gets stopped the moment primary goes down.

The switch from primary to secondary takes rough 45 seconds and the reconnect feature could connect to the secondary database