Re-sending, since it's looks like to be lost.

Just note: looks like the best fix is to copy message socket to force_socket struct inside transaction.

2014-10-21 13:33 GMT+04:00 Alekzander Spiridonov <alekz@li.ru>:
Hi list,

While going through an issue with multiple listen ip's I've found that while cloning the message tm doesn't save any info about the socket it was received on.

The question is: was it done on purpose or it's a bug? (e.g. for retransmitions timer prrocess is able to pick any(?) socket for sending message)/

--
Best regards,
Alekzander Spiridonov




--
Best regards,
Alekzander Spiridonov