First message never received when SUB binds and PUB connects
Description
Environment
OSX 10.6, libzmq-3.0 master
Activity
Martin Sustrik November 9, 2011 at 6:28 AM
Resolving as a duplicate of LIBZMQ-270.
Min RK November 8, 2011 at 11:43 PM
I just noticed that this is the same as LIBZMQ-270. Should I close this one as a duplicate, since that report has more specific information about how to fix it?
The symptoms reported are different (incorrect EVENT state vs lost messages), but the bug is the same.
Min RK November 8, 2011 at 12:52 AM
Is it possible for subscriptions to propagate from the SUB socket when they are made, rather than at the first call to recv? I assume that it should not be the case that behavior is not the same when SUB binds (everything sent prior to first recv is lost, no matter how long the wait between subscribing and receiving) as when PUB binds (everything sent after subscribe, but still prior to first recv arrives).
Martin Sustrik September 14, 2011 at 12:55 PM
This is caused by subscription forwarding. When connection is established, PUB starts sending messages, however, no subscriptions have yet arrived from the subscriber so it drops the messages.
PieterP September 4, 2011 at 9:52 PM
Presumably an error in subscription forwarding.
New in 3.0:
When SUB binds and PUB connects, the first message never arrives. Subsequent messages behave just fine, and the problem does not occur when PUB binds and SUB connects.