Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Connection Validation and Pool configuration #6212

Merged
merged 8 commits into from
Feb 5, 2024

Conversation

tnleeuw
Copy link
Contributor

@tnleeuw tnleeuw commented Feb 1, 2024

No description provided.

tnleeuw and others added 3 commits February 1, 2024 22:04
Only works for non-XA datasources currently, for XA datasources we need to still consider what is best to do as many XA drivers already implement pooling even if it's not configured.
@tnleeuw tnleeuw self-assigned this Feb 1, 2024
@tnleeuw tnleeuw linked an issue Feb 2, 2024 that may be closed by this pull request
maxLifeTimeSeconds = appConstants.getInt("transactionmanager.narayana.jdbc.connection.maxLifeTime", maxLifeTimeSeconds);
maxIdle = appConstants.getInt("transactionmanager.narayana.jdbc.connection.maxIdle", maxIdle);
maxLifeTime = appConstants.getInt("transactionmanager.narayana.jdbc.connection.maxLifeTime", maxLifeTime);
testQuery = appConstants.getString("transactionmanager.narayana.jdbc.connection.testQuery", testQuery);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All these extra/new features we set are valuable improvements, to my humble opinion, even though perhaps Ali's main issue was solved differently.

Copy link

sonarcloud bot commented Feb 5, 2024

Quality Gate Failed Quality Gate failed

Failed conditions

25.4% Coverage on New Code (required ≥ 65%)
C Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

idea Catch issues before they fail your Quality Gate with our IDE extension SonarLint SonarLint

@nielsm5 nielsm5 merged commit 281bf1e into master Feb 5, 2024
14 of 15 checks passed
@nielsm5 nielsm5 deleted the issue/6117_JdbcConnPoolSettings branch February 5, 2024 15:52
tnleeuw added a commit that referenced this pull request Feb 5, 2024
* Add Connection Pool Validation (#6119)
(Cherrypick from 8a26d34)
* PoolingJndiDataSourceFactory shouldn't check for DataSource to be XA or not XA (#6187)
* Try to determine if a datasource already does pooling (#6199)

Only works for non-XA datasources currently, for XA datasources we need to still consider what is best to do as many XA drivers already implement pooling even if it's not configured.

(cherry picked from commit 281bf1e)
@@ -30,6 +30,7 @@
</property>
</bean>

<bean id="dataSourceFactory" class="nl.nn.adapterframework.jndi.PoolingJndiDataSourceFactory" />
Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oei!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Db connections are left open in pool
3 participants