3 $ ${bindir:=.}/s4u-comm-failure "--log=root.fmt:[%10.6r]%e(%i:%a@%h)%e%m%n"
4 > [ 0.000000] (2:Receiver@Host2) Receiver posting a receive...
5 > [ 0.000000] (3:Receiver@Host3) Receiver posting a receive...
6 > [ 0.000000] (1:Sender@Host1) Initiating asynchronous send to mailbox2
7 > [ 0.000000] (1:Sender@Host1) Initiating asynchronous send to mailbox3
8 > [ 0.000000] (1:Sender@Host1) Calling wait_any..
9 > [ 10.000000] (4:LinkKiller@Host1) Turning off link 'linkto2'
10 > [ 10.000000] (2:Receiver@Host2) Receiver has experience a network failure exception
11 > [ 10.000000] (1:Sender@Host1) Sender has experienced a network failure exception, so it knows that something went wrong
12 > [ 10.000000] (1:Sender@Host1) Now it needs to figure out which of the two comms failed by looking at their state:
13 > [ 10.000000] (1:Sender@Host1) Comm to mailbox2 has state: FAILED
14 > [ 10.000000] (1:Sender@Host1) Comm to mailbox3 has state: STARTED
15 > [ 10.000000] (1:Sender@Host1) Waiting on a FAILED comm raises an exception: 'Cannot wait for a failed communication'
16 > [ 10.000000] (1:Sender@Host1) Wait for remaining comm, just to be nice
17 > [ 17.319588] (3:Receiver@Host3) Receiver has received successfully!
