Hi Tim,

You mentioned this previously in another email

'4.x makes this easier by introducing pinging, which will allow you to
reduce
the dead session expiration time on the server and have dead sessions
removed much quicker.'

I presume I can duplicate this by modifying our applications to ping the
server regularly?  I thought I read somewhere before someone doing that.  If
so what would be the optimum settings for Connection Timeout, Dead Session
Cleanup Interval and Dead Session Expiration.  At the moment Dead Session
Expiration is set to 43200.  Doesnt this sound a bit high (7 hrs?)?

Bottom line is we are still having immense issues with a client of around 20
users.  They get lockups often and I think this may have to do with
compounding incomplete transactions which dont get rolled back in a timely
fashion.

Thanks

Alex

Alex,

<< I presume I can duplicate this by modifying our applications to ping the
server regularly? >>

Yes.  Most of the 3.x users used something like the
TDBISAMSession.GetRemoteDateTime method to do so.

<< I thought I read somewhere before someone doing that.  If so what would
be the optimum settings for Connection Timeout, Dead Session Cleanup
Interval and Dead Session Expiration.  At the moment Dead Session Expiration
is set to 43200.  Doesnt this sound a bit high (7 hrs?)? >>

It isn't high if you're not using pinging.  But if you're using pinging,
then the dead session expiration time can be moved down to 30-60 seconds.
You can also move the session timeout setting lower, if you would like.

<< Bottom line is we are still having immense issues with a client of around
20 users.  They get lockups often and I think this may have to do with
compounding incomplete transactions which dont get rolled back in a timely
fashion. >>

If the lockup is occurring during a Post or another StartTransaction call,
then yes, this would be the cause.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Thanks for that.  What would be the optimum session timout and is that only
if we program pinging.

Alex

> You can also move the session timeout setting lower, if you would like.
>

Alex,

<< Thanks for that.  What would be the optimum session timout and is that
only if we program pinging. >>

90-120 seconds is fine.  You simply want to make sure that it's at least 30
seconds higher than the ping interval in order to allow enough time for the
pings to occur.

--
Tim Young
Elevate Software
www.elevatesoft.com