Skip to content

Resolving issue of being stuck at socket read#24

Open
Srthk wants to merge 1 commit into
dustismo:masterfrom
Srthk:master
Open

Resolving issue of being stuck at socket read#24
Srthk wants to merge 1 commit into
dustismo:masterfrom
Srthk:master

Conversation

@Srthk

@Srthk Srthk commented Jan 18, 2018

Copy link
Copy Markdown
  • Used a socket timeout set to a default of 30 seconds
  • Users of the library can change this value as per
  • Threads utilising this library will not get stuck eternally on socket read

Unit testing was carried out by artificially creating a socket to be in the hung state and beanstalk connections were timed out.

Code has been tested across our services for months now and works perfectly.

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.

2 participants