-
Notifications
You must be signed in to change notification settings - Fork 157
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
Under certain conditions, bulk import fails to acquire a db connection #2077
Comments
lmsurpre
changed the title
Under certain conditions
Under certain conditions, bulk import fails to acquire a db connection
Mar 12, 2021
lmsurpre
added a commit
that referenced
this issue
Mar 12, 2021
We used to have this attribute in our fhirProxyDatasource configuration, but we didn't carry it forward. After adding it to my deploy, I followed the steps to reproduce the issue described in #2077 and was no longer able to produce it. From the Liberty docs, here is what this setting does: > Specifies a timeout for validation of pooled connections. When specified, pooled connections are validated before being reused from the connection pool. The validation timeout is also used when the connection manager validates connections in response to a stale connection for PurgePolicy=ValidateAllConnections. A value of 0 means that connections are validated without applying any timeout. Validation timeout requires a JDBC driver that complies with the JDBC 4.0 specification or higher. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), or seconds (s). For example, specify 30 seconds as 30s. You can include multiple values in a single entry. For example, 1m30s is equivalent to 90 seconds. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Mar 12, 2021
We used to have this attribute in our fhirProxyDatasource configuration, but we didn't carry it forward. After adding it to my deploy, I followed the steps to reproduce the issue described in #2077 and was no longer able to produce it. From the Liberty docs, here is what this setting does: > Specifies a timeout for validation of pooled connections. When specified, pooled connections are validated before being reused from the connection pool. The validation timeout is also used when the connection manager validates connections in response to a stale connection for PurgePolicy=ValidateAllConnections. A value of 0 means that connections are validated without applying any timeout. Validation timeout requires a JDBC driver that complies with the JDBC 4.0 specification or higher. Specify a positive integer followed by a unit of time, which can be hours (h), minutes (m), or seconds (s). For example, specify 30 seconds as 30s. You can include multiple values in a single entry. For example, 1m30s is equivalent to 90 seconds. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Mar 15, 2021
issue #2077 - add validationTimeout to datasource dropins
I created a number of exports and imports. I waited over night. I did not hit an issue when executing again. I have tested with Db2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
I've seen it twice in a row by roughly following these steps, but I'm not sure if its always repeatable or not.
It fails with an error like this:
Expected behavior
It succeeds.
Additional context
I also have a
$healthceck
call that runs every 10 seconds or so.The text was updated successfully, but these errors were encountered: