Network Tranfer Rates

[James Booty]

Are there specific configuration settings that should be used for an interface thread that is connected via an Internet connection as opposed to being set up on a LAN or WAN connection. We are experiencing problems with keeping an Internet connected thread in an UP status. It seems to time-out and loses connectivity going to an OPENING status. The receiving system does not reflect a lost connection. This is only seen on the Interface Engine. Does anyone have a thread like this? Is there a way to make the thread less sensitive to transfer rates? Appreciate any help.

Topic

[Anonymous]

James,

My experience is that you can’t maintian an open connection across the internet.  The no activity timeouts on the internet are fairly short.  One option that we’ve used in the past was to use a upoc thread to basically start the outbound thread every so often and if there are messages to send they get sent, then the thread get’s shut down.

Are there any other suggestions out there for building an interface across the internet?

[Ryan Boone]

Sorry to be repetitive, but we have quite a few internet socket connections through VPN, and I used to have the same issues with timeouts/broken connections until I reduced the UNIX (AIX) “keepalive” setting from the default 2 hours to 15 minutes. 30 minutes may work as well but I don’t think 15 mins is a problem re: resources. The engine’s keep alive pulse is really determined by the UNIX level keepalive setting. Now we never have timeout problems. Sometimes a remote system will still go down (ie. when they do backups or maintenance) where they need to cycle the interface server to bring the connection back online. But other than that (and other “system issues”) the connections stay up even with little/no activity.

[Author]

Replies