Author Topic: PSDK connection keep alive  (Read 2407 times)

Offline bence.meszaros

  • Newbie
  • *
  • Posts: 6
  • Karma: 0
PSDK connection keep alive
« on: August 28, 2018, 10:48:45 AM »
Hi There,

I am using WarmStandby connection with reconnection to Outbound, Stat and T servers without any problem in our test environment however in production I keep getting "java.io.IOException: An existing connection was forcibly closed by the remote host" both on server and client side. It turned out that TCP Resets (RST) are sent by the F5 load balancer which resets "idle" network connections after 5 minutes.

Automatic re-connection and a ChannelListener with onChannelOpened did the trick of re-registering the events but it seems to be clumsy and error prone to me. I was told that resetting idle connections is a common practice by routers, load balancers and firewalls, and disabling it is currently not an option...
Have you ever seen this? What is the best practice here? A built-in keep alive trigger would do but I could not find anything like this on ClientChannel. Any idea to sort this out would be appreciated.
Thanks
« Last Edit: August 28, 2018, 10:57:26 AM by bence.meszaros »

Marked as best answer by bence.meszaros on August 29, 2018, 12:55:24 AM

Offline hsujdik

  • Hero Member
  • *****
  • Posts: 541
  • Karma: 30
Re: PSDK connection keep alive
« Reply #1 on: August 28, 2018, 10:56:07 AM »
The use of addp is for preventing that happen (among other issues it prevents). Lookup for addp in the docs

Offline bence.meszaros

  • Newbie
  • *
  • Posts: 6
  • Karma: 0
Re: PSDK connection keep alive
« Reply #2 on: August 28, 2018, 11:29:42 AM »
Whoa, that was fast. Indeed, this ADDP guy is what I need, many thanks.

Offline hsujdik

  • Hero Member
  • *****
  • Posts: 541
  • Karma: 30
Re: PSDK connection keep alive
« Reply #3 on: August 28, 2018, 12:04:42 PM »
Nice! Set it up before you open the Protocols