Hello Tim,
  I declare my self officially STUPID! STUPID! STUPID! running non thread safe code on a thread!!!
 Thank you for reminded me what has to be done property again.
 I fixed the query creation on my code and server is running WITH BufferedFileIO enabled fine for now
 
 This is explaining the freeze with BufferedFileIO disabled.

My apologies and thank you again!

Michael,

<< I declare my self officially STUPID! STUPID! STUPID! running non thread safe code on a thread!!!
 Thank you for reminded me what has to be done property again.
 I fixed the query creation on my code and server is running WITH BufferedFileIO enabled fine for now
 
 This is explaining the freeze with BufferedFileIO disabled. >>

I'm glad that you found the problem. Are you seeing some performance improvements ?

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<I'm glad that you found the problem. Are you seeing some performance improvements ?>>

For this project it defentely seems the loggin of the users to be faster (around 30-40 users) but i have to try into another app i have which has big tables soon. (it seems stable enough for putting into a production application)

Can you put a 2.28 beta of the manager too, so i can test the speed there ? (eg, reparing, optimizing etc)

Thank you

After a day of running i restarted the server and got: ElevateDB Error #601 The table Devices is corrupt (The index idxConnected is missing a required key).

Verification of the table Devices started at 2018-04-01 19:59:29.046
Verification error for the index idxConnected in the Devices table (Invalid index key value for row 4 (FALSE)) - Fixed
Verification of the table Devices ended at 2018-04-01 19:59:29.062

I'll turn off BufferedFileIO to see if that still happens ...

EDB 2.28 Beta 5:

BufferedFileIO Disabled = No corruption over 1 day, no freezes everything super !!!

Enabling BufferedFileIO again ... after a few minutes ... users are loggin and off ...
ElevateDB Error #100 There is an error in the metadata for the table Devices (A write operation did not complete and a repair is required).

Going into EDB Manager ... repair all tables ... result = no table is corrupted for crying out loud !!!

Tim a liitle help what might be ?

Michael,

<< BufferedFileIO Disabled = No corruption over 1 day, no freezes everything super !!!

Enabling BufferedFileIO again ... after a few minutes ... users are loggin and off ...
ElevateDB Error #100 There is an error in the metadata for the table Devices (A write operation did not complete and a repair is required).

Going into EDB Manager ... repair all tables ... result = no table is corrupted for crying out loud !!!  >>

You've still got an issue with your multi-threaded code.

Tim Young
Elevate Software
www.elevatesoft.com

Michael,

Hold on with my last reply - Terry Swiers has indicated that he's replicated a buffer manager error and will be sending more information soon.  So, I'll post here what I find out.

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<< Hold on with my last reply - Terry Swiers has indicated that he's replicated a buffer manager error and will be sending more information soon.  So, I'll post here what I find out. >>

Well i redesigned my server application from scratch (in order to find if it was my code) to use kbmMW threaded connection pool (the kbmMW way = TkbmMWEDBQuery) instead a thread safe EDBQuery and it seems to be working for a day with BufferedFileIO enabled.

IOW, now i'm using kbmMW to access the database exclusively with BufferedFileIO enabled. (Seems using both of them conflicting with, so the error appears when i use kbmMW and threaded EDBQuery together)

I can't think something else, let's see what Terry finds.

Tim,
 Updated the server, added an wrong SQL, fixed the SQL, rerun the Server:
 ElevateDB Error #601 The table Devices is corrupt (The index idxConnected is missing a required key).

 Verification of the table Devices started at 2018-04-09 00:01:08.758
 Verification error for the index idxConnected in the Devices table (Invalid index key value for row 2 (84.254.2.207:15925)) - Fixed

 I'm sure that there is a bug with multi-threading and BufferedFileIO ... I think it corrupts indexes.
 The problem will be to make a reproducable project for you ... I'll re-try ...

ps: the faulty SQL was
  SQL.Text :=
     'UPDATE "Devices"' + CRLF +
     'SET "RemoteLocation" = False';
and the correct is:
  SQL.Text :=
     'UPDATE "Devices"' + CRLF +
     'SET "RemoteLocation" = NULL';

RemoteLocation is VarChar

Thank you

Yes! Yes! Yes!

Testing 2.28 Build 7 right away with the old code
(kbmMW with thread safe EDBQuery)