Hi all,

Is there a recommended set of setttings for dbsrvr for average use?

e.g. deadsessions etc

dbisam 3.27

I have a customer who is reporting timeouts etc on connections occasionally.
I've never tweaked the settings from the default (apart from maxconnections)

thanks,

Steve

Steve,

<< Is there a recommended set of setttings for dbsrvr for average use?

e.g. deadsessions etc

dbisam 3.27

I have a customer who is reporting timeouts etc on connections
occasionally. I've never tweaked the settings from the default (apart from
maxconnections) >>

The default settings should work well as far as an "average" customer is
concerened.  When you say that they're getting "timeouts", do you know
specifically which DBISAM error that they're seeing ?  There are two
different types of timeouts - there are client-side timeouts and there are
server-side timeouts.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

I'll be going through their existing server setttings with them tomorrow, and getting more
info on the errors. The app has been in use a long time, but recently they have added a
lot more users including some remote ones coming over a wan using vpn over adsl lines,
which sounds like it could be causing the problems.

Just thought I'd see if there were any popular changes to make from the defaults that I
should know about first.

I just had another thought about a potential problem: the app itself has an automatic
logout when they don't press a key or click the mouse for so many minutes. This was
implemented years ago prior to client/server, but left in the later versions also as it is
useful to ensure everyone is out at night so db maintenance, export, import, backups etc
can run. It just does an application.terminate - should it do anything with the connection
first?

I've read other posts here about using a timer to keep the connection alive which sounds
like it might be a good idea in this case.

Thanks,
Steve



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Steve,

<< Is there a recommended set of setttings for dbsrvr for average use?

e.g. deadsessions etc

dbisam 3.27

I have a customer who is reporting timeouts etc on connections
occasionally. I've never tweaked the settings from the default (apart from
maxconnections) >>

The default settings should work well as far as an "average" customer is
concerened.  When you say that they're getting "timeouts", do you know
specifically which DBISAM error that they're seeing ?  There are two
different types of timeouts - there are client-side timeouts and there are
server-side timeouts.

--
Tim Young
Elevate Software
www.elevatesoft.com

Steve,

<< I'll be going through their existing server setttings with them tomorrow,
and getting more info on the errors. The app has been in use a long time,
but recently they have added a lot more users including some remote ones
coming over a wan using vpn over adsl lines, which sounds like it could be
causing the problems. >>

That's certainly possible.

<< I just had another thought about a potential problem: the app itself has
an automatic logout when they don't press a key or click the mouse for so
many minutes. This was implemented years ago prior to client/server, but
left in the later versions also as it is useful to ensure everyone is out at
night so db maintenance, export, import, backups etc can run. It just does
an application.terminate - should it do anything with the connection first?
>>

As long as the application shuts down in a controlled fashion, it should be
okay in terms of destroying the session(s) properly and logging out from the
database server.

<< I've read other posts here about using a timer to keep the connection
alive which sounds like it might be a good idea in this case. >>

We have this option in 4.x - pinging.  It is beneficial in cases where you
want to have any sessions removed immediately that are used by a client that
has gone down (or been permanently disconnected from the network for some
reason).  Because the client pings the server every X number of seconds when
it is up (where X is less than the connection timeout setting on the
server), it keeps the connection alive under normal circumstances.

--
Tim Young
Elevate Software
www.elevatesoft.com