[
https://issues.apache.org/jira/browse/ARTEMIS-2823?focusedWorklogId=491221&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-491221
]
ASF GitHub Bot logged work on ARTEMIS-2823:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Sep/20 13:53
Start Date: 25/Sep/20 13:53
Worklog Time Spent: 10m
Work Description: uomik edited a comment on pull request #3204:
URL: https://github.com/apache/activemq-artemis/pull/3204#issuecomment-698937509
One thing thats a little strange is that the pool had only three active db
connections at the time the error occurred (DBCP2 default max is 8, that should
be enough in most cases). Another peculiar thing was that I noticed that this
happened at exactly the same time on two of the four masters in the cluster.
This may actually be the same issue we've had with other applications with
this particular database server: the server randomly closes some of the
connections after one hour, being active or not. Based on earlier tests I
suspected that JDBC4 driver with isValid checks would be enough to cope with
this. I will first check whether the same pool configuration we use elsewhere
resolves the issue. If the problem persists will experiment with the other
options
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 491221)
Time Spent: 11h 20m (was: 11h 10m)
> Improve JDBC connection management
> ----------------------------------
>
> Key: ARTEMIS-2823
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2823
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Reporter: Mikko
> Priority: Major
> Time Spent: 11h 20m
> Remaining Estimate: 0h
>
> I have a case where the whole clustering reliability and HA must rely on HA
> capabilities of clustered database, and running on top of application server
> is not an option.
> The current JDBC store implementation is rather bare bones on the connection
> management side. JDBC driver is used directly with no management layer. At
> startup, the broker just opens couple of direct connections to database and
> expects them to be available forever. This is something that cannot be
> expected in HA production environment. So, similarly to the discussion linked
> below, in our case we lose the db connection after one hour, and all the
> brokers need to be restared to get new connections:
> [http://activemq.2283324.n4.nabble.com/Artemis-does-not-reconnect-to-MySQL-after-connection-timeout-td4751956.html]
>
> This is something that could be resolved by simply using JDBC4 isValid
> checks, but proper connection handling and pooling through datasource would
> be preferrable.
> I have implemented a solution for this by using DBCP2 datasource. Our test
> cluster has been successfully running this forked version since the release
> of Artemis 2.13.0. I will prepare of pull request if this is seen to be
> something that can be useful.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
