Tim,

> The issue is that the sleep mode appears to be shutting down the thread
that does the pinging in EDB.

So, the only way to come around this is to increase the serverside timeout.
Is this definitve, or a temperary workaround and is this something that
needs to be fixed on your side (I didnot notice it on other DBMS's, AFAIK)?

Regards, Harry



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:42FE6B30-CAA8-4D46-AED9-7E63B47DE4D1@news.elevatesoft.com...
> Harry,
>
> << I've been testing it again and it seems that when a user's pc (client
> side) is in 'sleeping mode', longer then the timeout, this appears.
> Then -when not not in sleeping mode anymore-, on browsing (or changing a
> filter- a filter was active in this case) the app freezes.
>
>  How to handle such a scenario. This ofcourse happens a lot (coffeebreaks,
> lunchbreaks etc). Is there a way to reconnect in these cases (so that a
user
> does not notice it)? >>
>
> EDB will handle it transparently, but it means increasing the server-side
> timeout to a very large value, thus defeating the pinging architecture's
> ability to quickly remove sessions that aren't pinging anymore.  The issue
> is that the sleep mode appears to be shutting down the thread that does
the
> pinging in EDB.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Harry,

<< So, the only way to come around this is to increase the serverside
timeout. Is this definitve, or a temperary workaround and is this something
that needs to be fixed on your side (I didnot notice it on other DBMS's,
AFAIK)? >>

There's no way for me to fix this if the OS is suspending the pinging
thread.  The OS trumps our code every time.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Ok, I understand, no hard feelings What's the way other users handle this
in real live then? Indeed increase the serverside
timeout, or are there other options? And what's the downside/pitfall of that
solution (if any)?.

Harry


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:85416E23-4B14-49CA-BDE0-4EBB654DAD26@news.elevatesoft.com...
> Harry,
>
> << So, the only way to come around this is to increase the serverside
> timeout. Is this definitve, or a temperary workaround and is this
something
> that needs to be fixed on your side (I didnot notice it on other DBMS's,
> AFAIK)? >>
>
> There's no way for me to fix this if the OS is suspending the pinging
> thread.  The OS trumps our code every time.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Harry,

<< Ok, I understand, no hard feelings What's the way other users handle
this in real live then? Indeed increase the serverside timeout, or are there
other options? And what's the downside/pitfall of that solution (if any)?.
>>

Actually, hold tight for the next build and I think I can get something in
there.  Apparently they snuck a new API call in Windows 2000 and higher
called SetThreadExecutionState that will allow me to prevent shutdown when
the pinging thread is running.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

That would be great!

Regards, Harry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:9E19632C-31E6-433D-BF82-9934438BB296@news.elevatesoft.com...
> Harry,
>
> << Ok, I understand, no hard feelings What's the way other users handle
> this in real live then? Indeed increase the serverside timeout, or are
there
> other options? And what's the downside/pitfall of that solution (if any)?.
>  >>
>
> Actually, hold tight for the next build and I think I can get something in
> there.  Apparently they snuck a new API call in Windows 2000 and higher
> called SetThreadExecutionState that will allow me to prevent shutdown when
> the pinging thread is running.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>