Message Format: Incomplete Msg to OB system

[Femina Jaffer]

Hi All,

We recently replaced a server to a new server for one of the sending applications.  We have exactly the same configurations in CL as we did in the previous server, with the exception of a new ip address.

The messages from CL and Out of CL seem to be in a correct format.  However, the messages received by the OB vender says that the messages are incomplete.  Meaning that some segments are SOMETIMES lost ; sometimes there is truncation.  However, this is not true for all messages.  In CL, we see the messages are intact coming and going out.

Would anyone have an idea of what is going on?  Could it be the ACK/NACK?  Is it something on the CL side or could it be on the sending application side?   Any advise would be much appreciated.

Thank you.

fsj

Topic

[Anonymous]

Hi Femina,

Try taking one of the “bad” messages in question and doing a hex dump on it.  Maybe there is something different about the segments that you can’t detect simply by looking at it in SMAT.   Take a known good message and one of the “bad” messages and compare them to see if there is any difference.  Also, look for anything that may be common to all of the “bad” messages (i.e.  are they always missing the same segments?  are they all the same message type?  are they all the same test type?).   Feel free to contact me at thomas.rioux@memorialhermann.org if you want to discuss this further.

Later….

Tom Rioux

[Femina Jaffer]

Thanks Tom, this is exactly what is being done for now.  I’ll let you know if we do not get this resolved.

Thanks again.

Femina

[Author]

Replies