>>> Is there a way to have the server terminate a long running
>>> transaction?
>>>
>>> I have a multi-threaded, multi-tier application with a FB 1.5.3 DB.
>>> Every once in a while a thread fails / leaks and I would like to find a
>>> way to kill the transaction within the thread. Since my application is
>>> losing it's handle to the thread I am hoping there is a setting on the
>>> server that can help me here.
>>
>> With Classic server you can task kill the corresponding connection,
>> but asides from that no.
>
> What a shame.
>
> Is there any way to specify a setting on the client to disconnect after a certain period of time?
>
> It does not seem logical to me that the garbage collector should wait indefinitely and thus peg the CPU.

1) Fix your applicaion. ("Every once in a while a thread fails / leaks")

If it does not help:

2) Tell us why do you think the problem is caused by garbage collector ?

3) And just to be sure - are you talking about _FB server_ eating CPU,
not client process (e.g. in active wait loop), right ?

Ivan