Firewall Timeout Issues

A

ahchel

New Member
We have a Progress Database 10.2b installed on Windows Server 2012 R2 and applications are running on Window 7 through a TCP/IP network.

Between server and client, there is an internal firewall which has 1 hour timeout setting. If it is idle over 1 hour, the client returned error “Error reading socket, ret=10054, errno= 2. (778)”. Then, the client session is kicked out but server login remains there.

Are there any setting that can keep both log in alive? or the connection can re-establish before kicked out?

Many thanks!
 
You need to change the firewall settings so that the connections is not killed after 1 hour. This setting is absolutely inappropriate for a client/server setup where the client has a persistent connection to the databse. You need to change the respecitive firewall setting.

  • The client will raise a STOP condition.
  • The database will clean-up ( release any locks ) as soon as it detects that the client has disappeared. This can take as long as you TCP keep alive setting is - which is usually around 30 minutes.
From a client perspective you could catch such a STOP conditon and roll you own re-connect. But that's not an easy task to do.
From the database perspective it can cause all sorts of trouble if clients disappear on a regular basis.

Heavy Regards, RealHeavyDude.
 
What RHD said.... just to expand a little here are your options

1) Change the firewall to stop the timeout for all ports
2) Change the firewall to stop the timeout for your range of ports (client server brokers)
3) Change the firewall to only timeout on specified ports like FTP,HTTP,etc.
 
You must log in or register to reply here.
Back
Top