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.

Sign up for GitHub

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

Jump to bottom

Synchronization issue with inproc: transport #62

Closed
hintjens opened this issue Sep 5, 2010 · 1 comment
Closed

Synchronization issue with inproc: transport #62

hintjens opened this issue Sep 5, 2010 · 1 comment

Comments

@hintjens
Copy link
Member

hintjens commented Sep 5, 2010

It looks as if doing a recv() on an inproc socket before another peer does a connect causes the recv() to block forever. I've a small program that reproduces the issue systematically on various boxes:

https://gist.github.com/09bd28120f3d9d39fdbf

This issue was tested with 0MQ/2.0.8.
@hintjens
Copy link
Member Author

hintjens commented Sep 5, 2010

This is a known issue with inproc:, where the bind MUST happen before the connect. I'm closing the issue now, it's not a bug.

csrl pushed a commit to exosite-archive/zeromq2 that referenced this issue Dec 22, 2012
@hintjens
Merge pull request zeromq#62 from da2ce7/master
59f71d6 
Fixed a Crash Bug only seen with unicode on Windows.
@LutzWeischerFujitsu LutzWeischerFujitsu mentioned this issue Mar 10, 2021
Open
benjdero pushed a commit to benjdero/libzmq that referenced this issue Feb 20, 2023
@sjmackenzie
Merge pull request zeromq#62 from hintjens/master
09c9ace 
Fixed delivery reports
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hintjens