Too many exceptions being thrown in FQ::RecvPipe about netmq HOT 8 CLOSED

I'm not sure what is the issue? anyway it's not only for the XHasIn, it's also for the recv message which should throw an again exception when their is no message available.

from netmq.

A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll
A first chance exception of type 'NetMQ.AgainException' occurred in NetMQ.dll

This is thrown over and over and over again.

It fills the debug log in visual studio and is also not great when the intention is just to signify that there's no message.
I can't tell without looking at the code whether it is an exception I need to worry about or not.

from netmq.

Can you provide code? I want to know if this happen in the Router.Recv or in the XHasIn...

from netmq.

also take a look at SocketBase.Recv, it's also using the again exception.

The issue is that in C# it's more common to use exceptions then error codes, the libzmq is written in C++ where it's more common to use error codes.

If the exception that flooding the debug log is being handled in the XHasIn maybe we can do something, but if it being handled in the socketbase.recv i'm not sure it's right do to something about it.

from netmq.

Don't know if this helps.

from netmq.

In my opinion (and without further analysing the code and only looking at the code @cwoode pasted) he is right: in this case it seems not to be exceptional behaviour and therefore it should not throw an exception which is catches at the next level.

cwoode [email protected] schrieb:

Don't know if this helps.

---

Reply to this email directly or view it on GitHub:
#57 (comment)

Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

from netmq.

OK, I'm working on a fix.

from netmq.

Fixed with pull request #66

from netmq.