For what it's worth, this situation should be vastly improved since 2.16.0
where dbcp2 was incorporated for connection management. See ARTEMIS-2823
[1] for more details.
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-2823
On Wed, Apr 22, 2020 at 9:45 AM ChrisSu wrote:
> I exactly h
I exactly have the same problem like mk666aim! Is there any solution for
this? Compare this stackoverflow thread:
https://stackoverflow.com/questions/60884155/activemq-artemis-jdbc-store-add-connection-pool-for-db-connections
Currently I send keep alive messages to my queues to keep alive the brok
I'm not terribly familiar with the JDBC support in Artemis or MySQL so
please bear with me. I've got a handful of questions:
1) Does MySQL just terminate any connection that exceeds the wait_timeout
no matter what or does it terminate connections that haven't had any
activity for more than the
Bumping this one.
I know that the JDBC persistence is under development, but a simple
connection maintenance should be considered an essential feature.
If Artemis can't stay up while connected to a MySQL server, then the feature
is not just experimental, but unusable...
mk666aim wrote
> We're t
We're trying to use MySQL 5.7 backend for JDBC persistent store.
This works fine, until the point where the connection goes stale due to the
server timeout.
This is our current set up in broker.xml:
jdbc:mysql://xxx:3306/artemis_datasource?create=true&user=mq_admin&password=abcd&useSSL=
