Open SteveHarveyUK opened 2 years ago
Further investigation appears to indicate that this is an issue with the SubscriberSocket. If I've followed the flow correctly it's failing while handling ZqmSocketOptions.Events in the Select and CommandType.ActivateWrite command.
Some how this is leading to an attempt to Swap to an invalid pipe.
It appears that this issue is mitigated by setting the highwater mark to 0 enough that the Subscribe socket doesn't need to invoke the Swap. I'd still argue that this is a bug.
Environment
Additional information on usage:
NetMQ is being used for comms between a client/server setup for the distribution of market data. The following sockets are used:
Expected behaviour
NetMQPoller running without exception.
Actual behaviour
NetMQPoller crashing with an internal exception:
Steps to reproduce the behaviour
Unfortunately, this appears to be happening at random periods, I'm hoping that someone will have an idea of how I can acquire further information regarding this exception. We have 16 instances of the server talking to 6 instance of the client but only one of the six clients appears to be seeing this problem. We've recently migrated these systems to AWS as hosted VMs and started seeing this issue. My guess is that it could be disconnection or connection recovery related.
Any ideas/comments gratefully received.