Receiving Port Goes Bad

[Mike Kim]

We are on a Windows box (QDX 5.3) and have a new ADT interface to Ibex (ER system). The interface will work for a while and then messages start to queue up on our end. When we restart, the thread stays in an opening state. This is a typical mlp_tcp client interface using recover_33.  There are no duplicate state 14 messages or anything else that I can see on our end. The only thing we can do to get it working is to change the port # on both systems, then stop and restart.  

Thanks in advance for your help!

Mike

Topic

[Jim Kosloskey]

Mike,

Have you looked in the process log to see if there is an indication of what caused the thread to go into an Opening state?

Have you tried stopping both sides; then bringing the Server (Receiving System) side up; then once that is up bringing up the Cloverleaf(R) Sending thread (without changing port numbers)?

If the above works, then that is usually an indication the receiving system went down and did not free up the port to allow a reconnect attempt.

What happens if you just stop the connection (assuming it is up) and then start it (when it is in a normall running state – not when the situation you observed is occuring)?

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Gina Borden]

We are on AIX, but we had similar issues when we went Live with IBEX.  We created a script that runs, and if we haven’t received anything within the last 5 minutes then we restart the thread on our side.  This seemed to resolve the issue for us.

[Mike Kim]

Thanks Jim!  Stopping and restarting both sides in the sequence you suggested did the trick.

Mike

[Jim Kosloskey]

Mike,

Good – now you need to contact the receiving system vendor and tell them to fix their communication facility.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies