Thanks, Miyako.
I had set both, but after your post I looked back at the docs for the
idle connections timeout and realized I misunderstood what was
happening:
From the v11 r4 LRM for Parameter #54:
"...When an idle connection reaches this limit, it is automatically
put on standby, which freezes
the client/server session and closes the network socket. This
functioning is completely
transparent for the user: as soon as there is new activity on the
connection which is on
standby, the socket is automatically reopened and the client/server
session is restored..."
So the term "timeout" as used with Parameter #54 is *significantly*
different from its meaning when used in Parameters #13 and 14.
But, given that, I'm curious why you suggest #13 should be set
shorter? From the documentation for #54, I would think this would be
unnecessary.
Bill
On Oct 27, 2009, at 9:43 PM, miyako wrote:
> Hi,
>
> have you set database parameter #54 (Idle Connections Timeout) and
> #13 (4D Server Timeout) ?
> both should be shorter than your firewall timeout (30 min).
>
> miyako
>
> On 2009/10/27, at 21:40, Bill Weale wrote:
>
>> I recently had a similar problem at a location where a new firewall
>> had been installed. I was told that a default, "out-of-the-box"
>> rule was to close all tcp connections which remained idle for 30
>> minutes or more.
>>
>> This was a CISCO ASA5505 series box, which I believe is fairly
>> common. If that is the case and if that will cause problems with
>> v11, it's probably something that should be "publicized" more.
>
**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase -
http://www.4d.com
4D Internet Users Group (4D iNUG)
FAQ:
http://lists.4d.com/faqnug.htmlArchive:
http://lists.4D.com/archives.htmlOptions:
https://lists.4d.com/mailman/options/4d_techUnsub: mailto:
4D_Tech-Unsubscribe@...
**********************************************************************
