Genesys TServer Idle timeout. Disconnection after 60 minutes

[Rogelio Gutierrez]

Hello All!

We have and java application client that is connected to Genesys TServer. Seems that after 60 minutes without activity, internaly the server is not connected (app is not getting any error or notification). When the client tries to use the TServer again, the requests are failing showing that the Tserver is not connected anymore.

Do you know what could be causing this?, there is a idle timeout configured in server side?, the client is able to modify this?. We try to modify timeouts from addp configuration object but we still seeing same issue.

Thanks!!!

[cavagnaro]

Weird...maybe you app is closing the TCP connection? Try to check the TCP settings of your computer or server. TServer shouldn't disconnect anything. Even addp is a ping pong protocol, so you need to indicate on your app to use it if you want it. If not, wouldn't matter. TServer will assume you are there and will accept requests from your app.

Enviado de meu E6633 usando Tapatalk

[PeteHoyle]

Maybe it's a firewall that is closing the connection.

If possible enabling ADDP in your Client is also a good idea

[n3vek7]

60 minutes is a typical timeout for an opened connection without activity for a firewall, you should look into this with your network team.

[Rogelio Gutierrez]

Thanks a lot for the responses.

We already have ADDP configured in our client. We are going to modify the server and client values and turn trace on in order to troubleshot this. Also we will keep an eye on the firewall behavior.