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

Socket receivebuffer less effective than possible [JDBC238] #287

Closed
firebird-automations opened this issue Feb 19, 2012 · 7 comments
Closed

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Relate to JDBC279

As the receivebuffer of the Socket is set after connecting the socket, it is less effective than it could be for buffer sizes >= 64 kilobyte as the window scaling option will not have been set in the handshake and the larger receive buffer size therefor goes unused (sendbuffersize is unaffected).

The implementation will need to be changed to use unconnected sockets, set buffer sizes and then connect.

Commits: 5fe0bea

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue relate to JDBC279 [ JDBC279 ]

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Scheduled for 2.3, if easy/small also backport to 2.2.2

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

assignee: Roman Rokytskyy [ rrokytskyy ] => Mark Rotteveel [ avalanche1979 ]

Fix Version: Jaybird 2.3 [ 10440 ]

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Committed fix in trunk. Decision for backport pending.

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

This was added to Jaybird 2.2.2 as part of JDBC279 / JDBC295.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 2.2.2 [ 10480 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Open [ 1 ] => Closed [ 6 ]

resolution: Fixed [ 1 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment