-
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
With the transaction timeout set unresonably low. a resulting error due to timeout does not reflect a timeout #2149
Comments
message from FHIR: Here is from the log: |
I added a stack trace of what this should look like at #2150 (comment) |
Re-tested this with the latest code with both 2 and 1 second timeout, and the error in the joblog is: |
Closing issue as the new timeout message is OK for figuring out that you have timed out. |
Describe the bug
A clear and concise description of what the bug is.
If you set the transaction timeout to something unreasonable like 2 seconds. this causes errors to happen that were not expected, and the reported error is not reflective of the fact you hit the transaction timeout.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Either have a reasonable minimum transaction timeout and a lower value is ignored with a log message at startup. Or always report errors related to transaction timeout as timeout errors.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: