You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Same for "expecting data" state as well, a read with a writer connected but no writes yet is in expecting data and won't honor a close.
More accurately, sequence of events is:
open read pipe
open write pipe
read one byte from the read pipe with no timeout -- blocks
send SIGALRM - read returns with EINTR
subsequent close on the read pipe blocks indefinitely
- Engine can now process PINGs while waiting for a READ to finish.
- Added extensive test cases to zpipes_server.c.
- Fixedzeromq#30 - can now close pipe while waiting for READ to finish.
- Fixedzeromq#26 - idle clients are disconnected (defaults to 60 seconds).
Symptom: when doing a blocked read and EINTR occurs, the server state was stuck in expecting chunk, and would't accept a close command.
Duplicate of issue #26, I think.
The text was updated successfully, but these errors were encountered: