I had LIBZMQ-307 happen to me in production recently. To note, I am using 3.0.2 (which I know is no longer supported), but I think it should be made sure that this isn't occurring in 3.1. If I have time later today I can try to do a test with 3.1, but am not sure yet if that will be possible.
On Tue, Feb 21, 2012 at 6:09 AM, Schmurfy <[email protected]> wrote: > Hi, > I added a new issue I found on the 3.1 master branch: LIBZMQ-325 > It allows to crash a server so I would consider it critical, two clients > can connect with the same identity but bad things happen when one of them > disconnects. > > > On 20 February 2012 17:33, Emmanuel TAUREL <[email protected]> wrote: > >> Hello Peter, >> >> On 20/02/2012 17:21, Pieter Hintjens wrote: >> > On Mon, Feb 20, 2012 at 9:24 AM, Pieter Hintjens<[email protected]> wrote: >> >> On Mon, Feb 20, 2012 at 6:49 AM, Emmanuel TAUREL<[email protected]> >> wrote: >> >>> - LIBZMQ-268 >> >>> - LIBZMQ-283 >> > These same to be the same problem? >> Not exactly. >> In LIBZMQ-268, the whole multipart message is lost (using PGM). In >> LIBZMQ-283, only the first part of the multipart message is lost using >> TCP. >> >> Thank's for your help >> >> Emmanuel >> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
