We got the same warning when resending messages from SMAT to an inbound thread on site X, when the messages had originally been saved to SMAT in the the outbound thread of site Y.
Our main ‘inbound HIS’ site performs generic transformation on the messages from the HIS and then sends them to multiple other sites which process messages for various ancillaries.
The other sites therefore have a main inbound thread which receives the messages sent from the HIS site, and then this inbound thread has the routes and route details to send to various ancillary outbound threads.
To save space, our main ‘inbound HIS’ site saves the outbound messages in SMAT, but the ancillary sites do not save the inbound thread’s messages, because they are exactly the same (and with multiple ancillary sites, you would have multiple copies of the same messages).
When resending a message in an ancillary site, we actually reference the HIS site outbound thread’s SMATDB and select that as the input thread in the Resend GUI. The ancillary outbound thread must also be selected as the outbound thread (see other discussions on this approach).
Most times this never presents a problem as long as you correctly select the inbound and outbound threads. However, if you are only selecting a single outbound thread, and this thread happens to have a protocol that does not expect/await replies (TCP ACK), then Cloverleaf complains with the above error message. I believe this is because the meta-data of the original message specifies await replies because that message originally came from the HIS site, from an outbound thread that had wait replies configured in the thread’s outbound settings.
When resending, you could uncheck the meta-data box, and you will not see those warnings, but the resubmit process takes a lot longer.
This is my theory anyway, just from observation.
Peter Heggie
PeterHeggie@crouse.org
.
