[zeromq-dev] Behaviour change between 4.1.5 and 4.2.1?

Luca Boccassi luca.boccassi at gmail.com
Mon Jan 16 12:26:01 CET 2017


On Mon, 2017-01-16 at 10:32 +0000, Simon.Giesecke at btc-ag.com wrote:
> Hi,
> 
> we have migrated from ZeroMQ 4.1.5 to 4.2.1 recently and I notice some behaviour change in some of our test cases. These cases are related to enforcing that some queues run full resp. the HWM is exceeded. Sorry I cannot be more precise at the moment; I tried to reproduce the behavioural differences with some reduced code example, but have not been successful so far. To enable me to facilitate a more focused reproduction of the issue, I have a general question in advance. Have there been any deliberate changes in behaviour between 4.1.5 and 4.2.1 that might be related to this? From reading the release notes, I did not find something that raised my attention.
> 
> Best regards
> Simon

One major change is that setting HWM works also after
connecting/binding, is that what you are doing?

There were many other bug fixes that can be seen in the git log, can't
remember all of them off the top of my head

Also what transport mode are you using?

Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170116/53d87d68/attachment.sig>


More information about the zeromq-dev mailing list