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

Implement Connection Pooling for User Queries #3819

Closed
rbeckman-nextgen opened this issue May 11, 2020 · 1 comment
Closed

Implement Connection Pooling for User Queries #3819

rbeckman-nextgen opened this issue May 11, 2020 · 1 comment

Comments

@rbeckman-nextgen
Copy link
Collaborator

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

Some channels run hundreds of database queries per second. It essential for those channels to have a pool of connections so that they are not constantly opened and closed, which is an expensive operation. I have created a JavaScript implementation of Hikari connection pool with two public methods, queryPoolDbConn() and updatePoolDbConn() and one private method, getPoolDbConn(). This implementation has proven itself to be well-performant and relatively robust. However, in some cases possibly caused by dropped DB connection, the Hikari DataSource fails to recover when the database gets back online and that requires restart of Mirth Connect.

Being a fundamental infrastructure facility, such implementation of connection pool is must be incorporated into the Mirth Connect application.

Imported Issue. Original Details:
Jira Issue Key: MIRTH-3939
Reporter: aitougan
Created: 2016-04-25T11:17:46.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

Duplicates MIRTH-2228

Imported Comment. Original Details:
Author: narupley
Created: 2016-04-25T11:19:18.000-0700

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

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.