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

catch all remote oshdb timeouts #258

Merged
merged 4 commits into from
Aug 18, 2020
Merged

catch all remote oshdb timeouts #258

merged 4 commits into from
Aug 18, 2020

Conversation

tyrasd
Copy link
Member

@tyrasd tyrasd commented Aug 11, 2020

When a timeout happens remotely (in the ignite cluster), the resulting exception which is thrown in the client might be nested in various levels of IgniteExceptions (depending on where in the code they are thrown precisely). This implementation recursively unwinds these nested exceptions, so that the original OSHDBTimeout exception is actually thrown in all cases.

Changes proposed in this pull request:

Type of change

Please delete if not relevant:

  • Bug fix (non-breaking change which fixes an issue)

Corresponding issue

Fixes GIScience/ohsome-api#10

Checklist

they might be nested in various amounts of `IgniteException`s (depending on where in the code they are thrown precisely). this implementation recursively unwinds these nested exceptions, so that the original `OSHDBTimeout` exception is actually thrown.
@tyrasd tyrasd added the bug Something isn't working as expected label Aug 11, 2020
@tyrasd tyrasd requested a review from rtroilo August 17, 2020 08:41
now, if the cause is found to be _not_ an oshdb-timeout exception, then the original wrapped (ignite) exception is thrown.
Copy link
Member

@rtroilo rtroilo left a comment

Choose a reason for hiding this comment

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

👍

@tyrasd tyrasd merged commit 04abd72 into master Aug 18, 2020
@tyrasd tyrasd deleted the fix-nested-remote-timeouts branch August 18, 2020 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as expected
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(early) timeouts in data extraction request return HTTP/500 instead of 4xx error code
2 participants