Thread stops in UP status. Must stop/restart

[Ross Stolle]

I have an inbound thread that has an HL7 message being left on a port on the interface engine.  For whatever reason, it intermittently will stop processing the message.  The thread stays in the UP status and all I have to do is stop/start the thread and everything takes off again.  Can anyone tell me what might be happening and how I can fix this?  Thanks!

Topic

[Michael Hertel]

Usually when something like this happens to us it is because

we have resent a smat message through the thread.

The tps procs generate an ACK and that is the message that is

hanging out there. Since the sending system on that thread isn’t

expecting an ack, it just stays there.

Sometimes the sending system will get screwed up with this

extra ACK and hang/pause/or shut down.

Since “use recovery database” does not apply to these messages,

we can simply bounce the interface and they’re gone.

[Dick Bly]

The fix is to write your inbound tps that creates the ack not to do it if the messages has a status of resend.  You could also not send an ack if the priority is greater than the default priority of 5120 and always do your resend with a priority of 6000

[Author]

Replies