- This topic has 5 replies, 3 voices, and was last updated 16 years, 2 months ago by .
We have had issues with several interfaces going to the same receiving system regarding message processing. It appears that messages are getting queued up on the Cloverleaf side and the thread still shows “up”. When I look on the receiving system’s side, everything looks fine there (the messages are not queued and the status shows “up”).
I turn off the ob thread on Cloverleaf and then go stop and start the corresponding thread on the receiving system’s side. I then bring the Cloverleaf side back up. When this is done, this works.
This issue occurred this morning, so, I went to the recovery database while the messages were still queued on the Cloverleaf side. All of the messages were in a state 11. I expected to see one message in a state 14. Does the fact that all of the messages for the ob thread were in a state 11 mean anything?
Has anyone had something like this happening? I am trying to find out what is causing the problem.
I have been asked to setup an alert to page the on-call person to know that the interface is not processing messages. Has anyone setup an alert to do something like this? I can’t figure out how I will setup the alert to know when to trigger without it being a false alarm. Sometimes the thread may actually be “up” and backed up with messages, but it is processing. This is mostly the ADT interface having this issue, so, I definitely don’t want to have anyone in an unnecessary panic. I also need to get a solution to this as soon as I can.
- The forum ‘Cloverleaf’ is closed to new topics and replies.