send() should not block when there are multiple endpoints where at least one endpoint is accepting transactions

Description

https://github.com/rbucker881/freelance_bug

The descriptions and justification of multiple connect endpoints and the connectivity info in the GUIDE are in conflict. I know it's too simple to say that the guide is right... it would be more helpful if the reference was.

SCENARIO:
--------
I have two servers (bind()) configured, only one is running
I have 1 client using PUSH in order to fan-out. If performs a connect() to both servers (only one running)
every other message going to the dead server instance is queued.
HWM=1, means that I lose one message
NOBLOCK means that I lose 1 message to the queue.

Environment

None

Activity

Show:

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

Created January 28, 2012 at 10:13 PM
Updated October 18, 2012 at 2:14 AM