I'm new to the forum and I know just enough about this topic to make me dangerous. This question is probably pretty basic to most of you, but here goes:

I've got two servers that I'm connecting to via TCP/IP. The issue is that I'm losing connectivity between the two after a certain period of inactivitiy. I know there is a default setting of 2 hours for the "tcl_keepidle" setting. We have played around with this setting on the server but now the issue appears to be with the client side. We thought that whenever the client side was ready to send a message, the connection would wake up and connectivity would be established. However, we are running into issues here now where some connections are not waking up and they are having to bounce the client side connection to get it to establish connectivity. As far as we know, there is no application setting that will resolve this.

Any ideas?

Thanks....Tom R.

Please, do not post your e-mail address, you are breaking one of this site rules:

(10) Don't post your email address and ask for an email reply. Don't send a private message with a technical question. The forums are for the benefit of all, so all Q&A should take place in the forums.

Excuse me....I should have read the rules better.....anyway, do you have an answer?

Geauxtn,
Please, "Edit" your original post and remove your e-mail address.

In regards to your Client/Server issue, I am not familiar with it.

Give some more time and an expert in the subject will help you.

Good luck!

What kind of applications are running at both ends ? If SSH, check this thread.

We have the Cloverleaf Interface Engine working as the server and the client is Eclipsys. I must note that we are not using the E-link interface engine provided by Eclipsys. The Cloverleaf server is a AIX server while the Eclipsys side uses a Windows server. We have both inbound threads to Eclipsys and outbound threads from Eclipsys. So far, we are only seeing the connectivity dropping on the outbound threads from Eclipsys. Would the tcp_keepidle setting only affect those ports where my side is acting as server in the tcp connection? Is there some type of setting on the Eclipsys side that would do the same thing? They were talking before about some "global timeout" setting on the Windows server.