Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/1576
@franz1981 It was an example. You could instead do what the text is
suggesting and just catch the SQLException and re-establish it yourself. My
point is to do the basic thing for the functionality to work, then optimise
later. We don't need a full connection pooling mechanism just to re-establish
a connection should one fail.---
