Has anyone configured their outbound thread to drop the connection after it has written a HL7 msg outbound and have it reconnect when another msg is ready to be sent?
I think I have it. Use close after write and delay connection until needed. Also, remove the recovery procs (save, kill, resend). There will be no validation of the ack either.
I found this option too and now I miss the ACK messages. I dont want that. Have you found a solution that starts and stops the thread and that can deal with the ACK handling?
I moved to the option of sending a heartbeat msg every 15 minutes. I know it’s unwanted traffic, but it seems to be working. I haven’t had any calls since I implemented it.
Yes. I built a fake msg and send it every 15 minutes via a cron job. The vendor had to work with me to accept and actually delete the msg after they received it.
.
.