(Semi-)Durable Subscribers and High-Water Marks examples close subscriber socket before END

Description

The Durable example here (http://zguide.zeromq.org/page:all#toc44) will "lose" the last messages if the subscriber is not up to see "END" message. I have only tested in Python and Perl but any mixture of the two will do.

When the Publisher program reaches the end the $publisher tcp socket remains open on 5565 waiting for the message's to be consumed, but the subscriber tcp socket on 5564 is closed, I assume by the auto clean up at the end of the program as there is nothing blocking it.

When the Subscriber program starts up again to retrieve the messages it can't synchronize with publisher and blats syn's at port 5564 that get reset.

Sorry only new to zmq (as demonstrated by going through examples) so not sure what the solution is as yet other than do something to keep the Subscriber port open while the Publisher has messages.

The reason for the investigation and jira is when pressing ctrl-c a couple of times as instructed to, the durable example seemed to not be durable =)

Environment

None

Attachments

1

Activity

Show:

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

Created June 11, 2012 at 10:45 AM
Updated June 11, 2012 at 10:45 AM