-
Story
-
Resolution: Done
-
Major
-
AMQ 7.4.1
-
Compatibility/Configuration
-
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
- causes
-
ENTMQBR-4397 FileConfigurationParser Does Not Handle Encrypted / Masked data-source-properties
-
- Closed
-
- incorporates
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is cloned by
-
ENTMQBR-4352 Doc: Improved JDBC connection management
-
- Closed
-
