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

revert 4fa2d5bc1ed8 to fix the regression introduced. Fixes [Issue 2180](https://github.com/pgjdbc/pgjdbc/issues/2180) #2183

Merged
merged 2 commits into from
Jun 16, 2021

Conversation

davecramer
Copy link
Member

No description provided.

@sehrope
Copy link
Member

sehrope commented Jun 16, 2021

Is this happening because the "non-blocking" read to check if notifications are available is blocking?

@davecramer
Copy link
Member Author

yes, this is a problem with ssl connections only. InputStream.read(...) blocks so we end up introducing a timeout on every interaction if there is nothing to read.

@sehrope
Copy link
Member

sehrope commented Jun 16, 2021

Dang. Out of scope for an immediate fix but maybe we can save the underlying socket and check that for availability regardless of whether it's replaced with an SSL wrapped one.

@davecramer
Copy link
Member Author

The real solution is to read the incoming data in a background thread. This solves many issues.

@davecramer davecramer merged commit 466bad1 into pgjdbc:release/42.2 Jun 16, 2021
@davecramer davecramer deleted the fixregression branch June 16, 2021 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants