strange save-delay (btrieve 8.x)

Hallo Btrivieans!

today we observe a very strange behavior at a PSQL 8.x server running on Win2000:

on client A there where updated some data, but this change of data was on client
B not visible:

at time t_0 I update a record in a btrieve-table (I got status code 0 on this
update) from cliant A

at time t_1>t_0 i look in that table from a client B<>A, and I see the record in
its state before t_0!

now I restart the session on client B at time t_2>t_1>t_0 and look again: now
the record has the changes from the update at time t_0!!

the application writes the updatetime in a special field of each record.
Say the updatetime before t_0 was t_b. than i could see this timestamp (t_b)
when i looked from B at time t_1. At time t_2 one can see, that the record was
updatet at time t_0(the correct time!).

So I guess, that the server does someting like write-chaching. This strange
delay occurs sometimes for new records (they look empty at first), but up to now
this where a matter of same secunds (strange enought!). But now, t_1-t_0 was
more than half an hour, and this is too long...

Does anyone know this pheanomenon and know, what one can do, to avoid this?

(I should say, that this occur not on all tables! and that the application uses
native btrieve-calls. I think, that on client A all looks(!) fine beween t_0 and
t_1. Further: the server was running since nov. 2004 without such a problem.).

Any hint will be welcome!

reagrds
M. Malarski

.

Relevant Pages

  • Re: Webservice running very slowly
    ... Looking at this it makes me think that its my client application that has ... There is currently very little load on the server because everyone has ... Enterprise solution if one doesn't have a production server running full ... Sorry I know thats not exactly quantifying ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: .NET Remoting performance problems
    ... that's very strange behavior indeed. ... consisting of a server application and a client application. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Strange DNS server change on a client.
    ... I was able to trace the problem, but still the behaviour looks strange. ... Changed it to local names server and all is OK. ... in Domain Group policy I had temporarily set DNS server to ISP's ... gpupdate the client gp also gets updated or not. ...
    (microsoft.public.windows.server.dns)
  • Re: why a non-blocking socket will block when call connect functio
    ... including that it tends to fix strange behaviour. ... > thanks for Arkady Frenkel's reply. ... do you mean "set SO_REUSEADDR in client" cause this problem? ... >> And don't set SO_REUSEADDR in client, that for server only BTW, ...
    (microsoft.public.win32.programmer.networks)
  • Re: OT Thin Clients
    ... While a thin client into a linux server at a command line level is no ... You normally run an X server on each client. ... You then set up the Linux server to accept multiple X ... and the X server running on the client displays it. ...
    (Fedora)