ACK’s Stuck in State 1

[mike brown]

I am in need of advice, I had a an issue yesterday where interfaces got stuck on the process bounce, when adding a table and messages were going to the error DB, I replayed some ADT messages that errored out from the inbound ADT from INVISION and now i have ACK’s stuck in state 1 and going no where because they are in EDCIDIC. is there anyway to correct this or do I have to just keep cleaning them out. below is how they look in the RDB

example

msg: 0x3000003c

Topic

[James Cobane]

Mike,

My guess is that in your reply handling proc, the reply messages aren’t getting dispositioned(i.e. KILL), thus it is hanging around in the recovery database. I would take a look at the reply handling proc.

Hope this helps.

Jim Cobane

Henry Ford Health

[mike brown]

Thanks James

Your answer got me to looking further at the messages that were sticking in state 1, I found we were having a memory leak on that filter proc i was using, the proc could not figure out what to do if a segment (PV1) i was filtering on did not exist, this caused the messages to hang in the RDB with no where to go. I fixed the proc to continue if it does not find a segment being filtered or killed if desired, we desired to continue the message we have other procs to kill them down the line.

Thanks for your answer

Mike Brown

[Author]

Replies