Greetings!

A question....

If our dbisam server is cycled, clients all fail with an 11280 error. The situation:

dbisam server starts
client connects
dbisam server is cycled
client gets 11280 error next time it tries a db operation


We traced the code, and see that dbisam has an internal reconnect function. We can see that this function is fired, but that it fails in some way and returns the 11280 error.

Is there a solution to this issue?

Thank you!

(my reference is 25724)

Sam,

<< If our dbisam server is cycled, clients all fail with an 11280 error. The
situation:

dbisam server starts
client connects
dbisam server is cycled
client gets 11280 error next time it tries a db operation

We traced the code, and see that dbisam has an internal reconnect function.
We can see that this function is fired, but that it fails in some way and
returns the 11280 error. >>

You cannot reconnect a client application's remote session after the
corresponding server session has been freed on the server.  You'll have to
close the remote session in the client application, and then restart it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thank you for the update!

We reproduced the problem by cycling the server, but out in the real world, this is happening while the server stays up (but it does some backups, and other automatic tasks at night).

Questions are:

a) Might the server be closing idle session by itself?
-- What control do we have in this area?
-- Can the server do logging of this kind, so we can see what is going on ?


>> [RE server restart] You'll have to
>> close the remote session in the client application, and then restart it.

Can this be automated within the dbisam client code, or must it be it our higher level?


Thank you!!

Hi Samjones,

We've experienced similar scenarios with some of our projects if the
server is under a tremendous load and causes certain applications to
become unresponsive for a few minutes. (Normally if the remotetimeout is
exceeded).

The application asks if you want to keep waiting. Choosing Yes just
causes the application to try again and show the same message after the
remotetimeout period again. (even if the server has finished it's other
task), and continues in this loop.

We have also found this issue can occur if the user executes a
query/report that takes longer to resolve than the remotetimeout property.

Increasing the remotetimeout setting fixed the issue for us. Your issue
sounds slightly different, but it might be worth a shot anyway?

Cheers

Adam.

Thanks!

The answer seems to be the one discussed here:

http://www.elevatesoft.com/forums?action=view&category=dbisam&id=dbisam_cs&msg=3913&page=23

Adam,

<< The application asks if you want to keep waiting. Choosing Yes just
causes the application to try again and show the same message after the
remotetimeout period again. (even if the server has finished it's other
task), and continues in this loop. >>

How do you know that the server has finished its other task in this case ?
If you can nail this down to a specific set of circumstances, please let me
know.  I haven't seen anything like this, at least not in the last few years
of DBISAM.

I wouldn't recommend increasing the remote timeout, because it shouldn't
make any difference, and may end up giving the user the impression that the
application is hung.  The general idea is that you want to let the user know
as soon as possible that the remote session is waiting on the operation on
the server to complete.  The best way to do this normally is to make sure to
always show progress on the client side.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> << The application asks if you want to keep waiting. Choosing Yes just
> causes the application to try again and show the same message after the
> remotetimeout period again. (even if the server has finished it's other
> task), and continues in this loop. >>
>
> How do you know that the server has finished its other task in this case
> ? If you can nail this down to a specific set of circumstances, please
> let me know. I haven't seen anything like this, at least not in the last
> few years of DBISAM.
>
> I wouldn't recommend increasing the remote timeout, because it shouldn't
> make any difference, and may end up giving the user the impression that
> the application is hung. The general idea is that you want to let the
> user know as soon as possible that the remote session is waiting on the
> operation on the server to complete. The best way to do this normally is
> to make sure to always show progress on the client side.

I'm confused...

In this post
http://www.elevatesoft.com/forums?action=view&category=dbisam&id=dbisam_cs&page=23&msg=3923#3923
(last reply) you mention to increase the remotetimeout property. (Which
works)

I'll see if I can replicate the set of circumstances at some stage and
get back to you.

From memory what I've seen happen is that when the server has a really
large query (and maybe unoptimised) it can take longer than the
remotetimeout property to process and this normally leads to a message
being prompted to the user asking if they want to remain connected which
sets the StayConnected property to true, but for some reason it doesn't
seem to relink. (They keep getting that message appear over and over
again, even when it appears as though the server has finished executing
the query).

In the past increasing the remote timeout property fixed the issue and
has been my workaround todate.

Cheers

Adam

Adam,

<< In this post
http://www.elevatesoft.com/forums?action=view&category=dbisam&id=dbisam_cs&page=23&msg=3923#3923 (last reply) you mention to increase the remotetimeout property. (Which works) >>I also say "or define an OnRemoteTimeout event handler".  The preferentialway of dealing with this is to define the event handler and let the usermake the decision as to keep waiting, or to disconnect.<< From memory what I've seen happen is that when the server has a reallylarge query (and maybe unoptimised) it can take longer than theremotetimeout property to process and this normally leads to a message beingprompted to the user asking if they want to remain connected which sets theStayConnected property to true, but for some reason it doesn't seem torelink. (They keep getting that message appear over and over again, evenwhen it appears as though the server has finished executing the query). >>If you can send me something that replicates this, I'll be happy to take alook at it.  I've tried to replicate this here, but without any luck (Ibasically just breakpoint the server code so that it doesn't return for avery long time.--Tim YoungElevate Softwarewww.elevatesoft.com