[ARTEMIS-2918] Support Server restart on I/O errors

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Won't Do
• Affects Version/s: 2.15.0
• Component/s: Broker
• Assignee: Francesco Nigro
• Reporter: Francesco Nigro
• Created: 25/Sep/20 16:15
• Updated: 18/Dec/20 20:06
• Resolved: 18/Dec/20 20:06

Description

Currently the JDBC journal already provide a periodic lock evaluation both for live and backup using HA shared store, but the default strategy on failures is to suicide the broker: a different strategy could be to unify the behavior seen for the file-based version (https://issues.apache.org/jira/browse/ARTEMIS-2421) and making use of the recent changes on https://issues.apache.org/jira/browse/ARTEMIS-2823 using connection pooling to be more resilient to network glitchs too.

 

This translate into supporting a feature similar to classic ActiveMQ's restartAllowed one, although it could be applied only on I/O failures because Artemis doesn't use a container to manage its instance.

Issue Links

• requires: ARTEMIS-2823 Improve JDBC connection management
• links to: GitHub Pull Request #3289