>
> Rodrigo,
>
>
>
> There is unfortunately no simple way of tracing such behaviour through
> your application. If you have a test database to use, you can write
> yourself a shell that creates and commits a new transaction every 100
> ms or so, then look for particular behaviour that sticks the

transactions.

>
> Adam
>

Hi,

thanks for answering. I've already done a test with
commit/commitRetaining and indeed they perform different (sadly).

Is there a way to prevent the long running transactions from existing?
I've thought about a way to prevent long running transactions on the
main part of our application, but for minor parts it would be a lot of
work. If we could just kill the long running transaction, we would be
able to trace where this is happening and prevent that. Maybe a
magical parameter of firebird.conf? :-)


Regards
Rodrigo