Version 5.5 TCP/IP socket issue when connection lost

[Sam Craig]

We went live with Cloverleaf 5.5PRev1 March 31st.  Since then all has been great, except for one small issue.  When a recieving system goes down or network connection drops, the interface goes to an “opening” state.  Then when issue resolved, it goes back to an “up” and connected state, but will not transmit messages from recovery log.  We have to manually stop/start the thread and then it connects and transmits messages OK.  Did not have to do this on old 5.2 version.  Any thoughts?

Sam

Topic

[Michael Hertel]

Does this happen all the time / everytime?

I’m thinking that the interface may be waiting for an ACK and that you don’t have timeout/retries configured to resend after x amount of time.

[Author]

Replies