Drop connection after write

This topic has 6 replies, 2 voices, and was last updated 14 years, 9 months ago by Roderick Derks.

Creator

Topic
August 3, 2009 at 7:05 pm #51097

Todd Yingling
Participant

Hello,

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?
Creator

Topic

Viewing 5 reply threads

Author

Replies
- August 4, 2009 at 2:06 pm #68785
  
  Todd Yingling
  Participant
  
  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.
- November 25, 2009 at 4:42 pm #68786
  
  Roderick Derks
  Participant
  
  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?
  
  Roderick
- November 25, 2009 at 4:52 pm #68787
  
  Todd Yingling
  Participant
  
  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.
- November 25, 2009 at 4:53 pm #68788
  
  Roderick Derks
  Participant
  
  You mean sending a fake message?
- November 25, 2009 at 4:57 pm #68789
  
  Todd Yingling
  Participant
  
  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.
- November 25, 2009 at 5:16 pm #68790
  
  Roderick Derks
  Participant
  
  Thank you Todd.
Author

Replies

Viewing 5 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.