Garry,
If you have ‘Outbound Only’ checked then any DATA messages received are ignored, otherwise DATA messages are passed into Cloverleaf(R).
Now how does Cloverleaf(R) know what is a DATA message versus a REPLY?
If you have Await Replies checked, then a switch is thrown when an outbound message is sent which essentially says the next message RECEIVED is a REPLY. Once the REPLY is received the switch is turned off. Once the switch is turned off, any messages received are treated as DATA messages. If ‘Outbound Only’ is checked any DATA messages received are ignored at the protocol level.
If ‘Outbound Only’ is not checked, then any DATA messages received are passed on and you must handle them.
The only time I have had an Outbound thread where I do not have ‘Outbound Only’ checked is in a Query/Reply integration wherein the replies (really DATA) are received over the same thread. I tend to like to have true Asynchronous message delivery technique deployed for Query/Reply integrations and have the replies come over another connection so I would have the ‘Outbound Only’ checked on the Query thread (the Replies coming in on another thread).
If you turn the engine noise level up all the way you will see this activity.
In my opinion, if the connection is supposed to be for the sending of DATA one way only, then the receiving system has an issue they need to address.
In an earlier version of Cloverleaf(R) there was an issue wherein the switch for Awaiting Replies was not reliably thrown related to timeouts and replies were being treated like data. I have not seen that recently.
Jim Kosloskey
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
.
