Re: TCP connection timeout

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hiya Jim,

I'm not sure I understand.  I assume you're seeing this in NETSTAT, if 
so what state does it say that the sockets are in?

If it's TIME-WAIT, that's a normal condition, it has to do with the way 
TCP/IP works.  It's not something I can control.  The only thing you can 
do is adjust CHGTCPA TCPCLOTIMO() and change it to a shorter timeout 
value.  It can't be controlled from the software.

But, if they are sitting around in FIN-WAIT or or ESTABLISHED, then 
something is wrong.  Not sure what would cause that, other than HTTPAPI 
ending abnormally?


On 3/28/2011 1:34 PM, Jim Bostwick wrote:
>
>     We are using HTTPAPI (1.23) `http_url_post_stmf' to get information
>     from a 3^rd party and it has been working really well for several
>     years.  We recently migrated to a new power 7 system and have noticed
>     that the TCP connections are not being closed in our application when
>     the RPG pgm ends, but rather after they timeout via the iSeries TCP
>     settings (currently set to 120 seconds).  We run these requests via a
>     single threaded jobq in batch, but they are running so fast now, that
>     we are seeing occasional timeout errors, and I am thinking it may be
>     because we are hitting the 3^rd party site with another request, while
>     we already have several earlier requests that have not yet `timed
>     out'.
>
>
>     Is this something that may be fixed in the current beta, or is there
>     something that I can change in our RPG program to force the connection
>     to close when it ends?
>
>     Jim
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------