I believe this is a bug in how jeromq handles Thread interrupts. If I close it by other means, the ESTABLISHED connections are no longer.
On Wed, Aug 14, 2024 at 5:46 PM Trevor Bernard <[email protected]> wrote: > > Gentlemen, > > I'm working on a potential Jeromq bug (Issue #993) and I'm seeing > behaviour that I don't understand. You can follow my work here: > https://github.com/trevorbernard/jeromq-993 > > Here is my conundrum. > > The issue states additional SYN packets are sent from closed DEALER > sockets with the Context intact. I don't see this behaviour. But what > I do see is from the ROUTER, the socket connections remain ESTABLISHED > for all the closed sockets. Is this expected behaviour? E.g. I created > 1 ROUTER and 5 DEALER sockets closing the first 4 DEALERS and leaving > the last connected. > > This is the typical output > $ netstat -ant | grep 10.10.0.1:5555 > tcp 0 0 10.10.0.1:5555 0.0.0.0:* LISTEN > tcp 0 0 10.10.0.1:5555 10.10.0.1:38412 > ESTABLISHED > tcp 0 0 10.10.0.1:5555 10.10.0.1:38404 > ESTABLISHED > tcp 0 0 10.10.0.1:5555 10.10.0.1:38418 > ESTABLISHED > tcp 0 0 10.10.0.1:5555 10.10.0.1:38446 > ESTABLISHED > tcp 0 0 10.10.0.1:5555 10.10.0.1:38434 > ESTABLISHED > tcp6 0 0 10.10.0.1:38446 10.10.0.1:5555 > ESTABLISHED > > The ROUTER is cpp and the DEALER is a jeromq. _______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
