[zeromq-dev] Seldom publisher is not listened to for long ?

Michael Holm Michael.Holm at tibra.com
Mon May 16 10:57:53 CEST 2011

2011/5/16 Martin Raspaud <martin.raspaud at smhi.se>:

> I have a very simple pub/sub scheme (1 pub, 1 sub) talking over an IPSec
> tunnel.
> This seems to work great when publishing messages regularly. However, a
> typical use case for us would be to publish one message every two or
> three hours. In those cases we have noticed that the subscriber after a
> while is just not receiving any messages anymore (no obvious error
> message or so).
> We fixed the problem by implementing a heartbeat, but I'm a bit
> sceptical. ZeroMQ should know better, right ? Or maybe is this not a zmq
> problem, maybe it's related to an underlying network layer ? Does anyone
> have an idea on this ?

It's possible the tunnel itself has a timeout for inactivity, and you
can presumably raise this. Sending a keep-alive heartbeat is an OK
workaround but obviously not as good as understanding what's actually
going on.


IPSec tunnels typically disconnect after a time period and then will automatically reconnect as soon as someone tries to access a vlan routed over that connection. What is weird is that if you have an established socket connection I would think that is enough to keep the tunnel alive. There might be an option set on the tunnel that disconnects after n minutes if no traffic has been sent even if there is an existing connection. You need to chat with the team responsible for setting up the tunnel.


Tibra Trading Europe Limited is Authorised and Regulated by the FSA (Company No. 06061713)
Tibra Global Services Pty Limited London Branch (Company No. BR014370)
Tibra Equities Europe Limited (Company No. 07283912)
Registered in England & Wales - Level 11, 5 Aldermanbury Square London EC2V 7HR

The contents of this email including any attachments are confidential.  If you have received this email in error, please advise the sender by return email and delete this email.  Any unauthorised use of the contents of the email is prohibited and you must not disseminate, copy or distribute the message or use the information contained in the email or its attachments in any way.

The views or opinions expressed are the author's own and may not reflect the views or opinions of Tibra. Tibra does not guarantee the integrity of any emails or attached files. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments.

More information about the zeromq-dev mailing list