-
Notifications
You must be signed in to change notification settings - Fork 32
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
connection.query timeout do not work #167
Comments
@bubnenkoff I don't see any trivial bug in the timeout parameter handling. Is there any way you could provide a reproducible code with the related DB setup? |
To reproduce you need set long timeout here:
And to try run long request here:
In result you will get error:
See code here https://stackoverflow.com/questions/69041494/timeoutexception-on-query-cache-class |
@bubnenkoff I'm not able to check this until later, to help the debugging, could you check it at what |
I am having the same issue here. It breaks at 30 seconds.
I am using both the timeoutInSeconds property, and as I am using futures, I am setting the timeout of the futures to 2 hours.
Everything is in a try catch block, it gets the error, but there is no stack information. Could it be related to any configuration in the server instead of the library? @isoos if you point me to the right place of the library to narrow the search I can take a look |
@pedropastor: the package has moved to a new repository (and new versions). Please use that for further help. |
timeoutInSeconds
in:do not work, My code is fall with timeout exception:
Future not compeleted
on long queries.query timeouts sets only if they are setting on connection:
But setting in
connection.query
are should work because:The text was updated successfully, but these errors were encountered: