We are seeing strange behavior of "remote_idle_timeout"-option for SQL Anywhere 16.0.0.2798.
Timeout occurs after double the number of seconds. For example:

1) set temporary option "remote_idle_timeout" = 30;

ASA (-o) log (30 * 2 = 60 seconds!):

I. 06/10 11:59:31. CONNECTION_PROPERTY('remote_idle_timeout')=30
I. 06/10 12:00:32. SQLCODE = -982, SQLSTATE = WW051, ERRORMSG() = Connection timed out

Web (-zoc) log:

[connid = 28, 06/10 11:59:31.446]
[connid = 28, 06/10 11:59:31.446, REQUEST]
POST /d4w/api/getNewBookingsLong HTTP/1.0
Accept-Charset: windows-1251, UTF-8, *
Date: Mon, 10 Jun 2019 08:59:31 GMT
Authorization: Basic ...
Host: ....com
User-Agent: SQLAnywhere/16.0.0.2798
Connection: close
Content-Type: application/xml; charset=UTF-8
Content-Length: 0

[connid = 28, Timeout]
[connid = 28, socket closed]
[connid = 28, Error: socket closed by peer]

2) set temporary option "remote_idle_timeout" = 80;

ASA (-o) log (80 * 2 = 160 seconds!):

I. 06/10 12:03:25. CONNECTION_PROPERTY('remote_idle_timeout')=80
I. 06/10 12:06:06. SQLCODE = -982, SQLSTATE = WW051, ERRORMSG() = Connection timed out

Web (-zoc) log:

[connid = 28, 06/10 12:03:25.652, REQUEST]
POST /d4w/api/getNewBookingsLong HTTP/1.0
Accept-Charset: windows-1251, UTF-8, *
Date: Mon, 10 Jun 2019 09:03:25 GMT
Authorization: Basic ...
Host: ....com
User-Agent: SQLAnywhere/16.0.0.2798
Connection: close
Content-Type: application/xml; charset=UTF-8
Content-Length: 0

[connid = 28, Timeout]
[connid = 28, socket closed]
[connid = 28, Error: socket closed by peer]

Is this doubling the timeout wait correct?

ps: When the connection is interrupted by the web service, we get the following error:

I. 06/10 12:20:59. SQLCODE = -983, SQLSTATE = WW052, ERRORMSG() = HTTP request failed. Status code '504 Unused'