Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/1576
@franz1981 @clebertsuconic The reason we don';t use connection pools is to
increase performance on journal syncs. Each time a connection is released back
to the pool, the prepared statements need to be reinitialized. @franz1981 I am
not sure your statement is correct:
```
ie if the connection drop, no reconnection will happen.
```
Did you look to see if reconnects are handled by the JDBC driver? I'd
expect the JDBC client libs to take care of reconnects after a drop, meaning we
don't have to think about this at the application level.
We may at some point in the future want to manage our own connection pool.
SQLFileFactory would benefit from this. At the journal level, we would need to
refactor to sync at the operational context level. I'm not against using the
Connection Pool to handle the optmistic lock, as it doesn't affect perf. But
please ensure your assertion is correct before proceeding :).
---
