timeout condition

[Brad Dorr]

We are running QDXi 5.2 on AIX.  We have our Outbound threads setup as follows using the recover 33 procs:

save_ob_msg as the proc for send OK Procs

Await replies is checked with a value of 30

resend_ob_msg is the proc used for reply gen.

check_ack is the TPS inbound reply proc.

We are seeing this condition.  If the tread has a TCP/IP connection established with the application’s interface, but a timeout condition occurs.  Meaning we sent them a message but we didn’t get a ACK nor a NAK back from them in 30 seconds, we just didn’t get any reply then we timeout and send the message again.  This logic is fine except that the message gets written to SMAT over and over again every 30 seconds until the TCP/IP connection is broken or we get a reply back from the applications interface.

Has anyone ever seen this?  Is there a way to correct it?  It looks like since TCP/IP gets an ACK back because the IP connection still exists that Cloverleaf writes the message to SMAT even though it was timeout condition.

Can anyone shed some light on this issue?

Thanks,

Topic

[Rentian Huang]

Brad,

Are you talking about the IB or OB SMAT? We have resend_ob_msg in the reply gen, but we don’t have such a problem.

If I understand correctly, when TIMEOUT happens, msg state change to State 2 before it goes to the Xlate again.

It would be interesting to know between what states does the Engine saving the IB/OB SMAT.

Just some hints..

Sam  🙂

[James Cobane]

Brad,

The engine writes to the SMAT file upon successful reads from the protocol thread (for inbound save) and successful writes to the protocol thread (for outbound), so I don’t believe there is a way to avoid having a ‘resent’ message write to the saved message file.  Essentially, whenever you would see the ‘Msgs In’ or ‘Msgs Out’ count increase is when the message would be written to its respective saved message file.

Hope this makes sense.

Jim Cobane

Henry Ford Health

[Author]

Replies