[Quickfix-developers] i'm seeing deadlocks...

[Mark T. K. <mke...@di...>]

... while writing to the 'signal' socket (pipe) used to implement
non-blocking sends.

i have a test where i send 6,000+ orders in a batch and receive 6,000
acks and 6,000 fills in response.  in the middle of it, i shut down
and restart a proxy that sits between the sender and the exchange
simulator.  every now and then, this triggers a deadlock in the
exchange simulator (see the attached stack trace).

since a write to the 'signal' socket can block, sendToTarget can
still block, and that restores the oft-discussed deadlock scenario
that the non-blocking send implementation sought to avoid.

thoughts/comments?  i'm using the trunk for my tests, not 12.4.

/mark


This communication and any attachments may contain confidential/proprietary information and is intended for information purposes only. It is not an invitation or offer to purchase interests from Diamondback.  Any representation to the contrary is unintentional.  This communication is intended only for the person(s) to whom it is addressed.  If you are not the intended recipient you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message or any attachments is not permitted.  If you have received this in error, please notify the sender immediately by e-mail and delete this message.  All e-mails sent to or received from this address will be received by Diamondback's company e-mail system and is subject to archival and possible review by someone other than the recipient.  This notice is automatically appended to each e-mail message leaving Diamondback.