<Snip>

> >I can provide full details and even a database example if needed.
>
> 1. Try changing the GCPolicy(in firebird.conf) to background
> 2. Don't run a MON$ transaction in high load conditions
>
> ./heLen
>

I tried the fix, but it won't help.

The tests are being performed on a completely unloaded machine (no
high load conditions), with default config file (ie everything
commented out) and with and without a

GCPolicy = background

clause.


I went onto checking the log file and indeed there's something "odd":

ASYTO01 (Server) Fri Nov 28 11:02:35 2008
Shutting down the Firebird service with 3 active connection
(s) to 1 database(s)


ASYTO01 (Server) Fri Nov 28 11:02:35 2008
The database <Snip>\BIN\MEASURES_DATABASE.FDB was being
accessed when the server was shutdown


ASYTO01 (Server) Fri Nov 28 11:02:35 2008
Fatal lock manager error: invalid lock id (23100), errno: 0


ASYTO01 (Client) Fri Nov 28 11:12:32 2008
Guardian starting: "C:\Program Files\Firebird\Firebird_2_1
\bin\fbserver.exe"



ASYTO01 (Server) Fri Nov 28 11:19:24 2008
Shutting down the Firebird service with 2 active connection
(s) to 1 database(s)


That is, I see this "invalid lock" message and several (I only posted
a snippet) of those "shutting down .... with X active connection",
despite both our application and EMS and IBExpert were started with a
freshly started up Firebird daemon, worked only on 1 database and
then Firebird would be shut down (due to 100% CPU usage).

Notice neither our applications nor EMS / IB give any error message
and everything works perfectly, just slow like a crawl.