Subject | Re: [firebird-support] Re: Commit Client Transaction - Monitoring Tables |
---|---|
Author | Helen Borrie |
Post date | 2008-10-01T01:31:13Z |
At 11:07 1/10/2008, you wrote:
In 2.x you can specify a timeout for WAIT transactions (isc_dpb_lock_timeout argument in the ODS 11+ API). But, even if you are using Fb 2.x on an ODS 11.x databases, it's not likely this is surfaced in any version of IBX. Considering the fervour with which IBX's maintainer Jeff Overcash refuses to implement support for Firebird improvements, I would love to be proven wrong. ;-)
./heLen
>Thanks for taking a crack at it. I actually have stepped through the IBX code to the point where it calls the following method from the client libraryYou are using WAIT transactions in your threads, which is a hang-up waiting to happen. Your COMMIT calls only *request* a commit. They won't return until waiting transactions are able to either commit or throw lock conflicts. You're only getting what you asked for...you really need to assess what benefit you're getting from running WAIT transactions in user-initiated threads.
>
>isc_commit_transaction
>
>This is where the trail ends and does not step to the next line of code.
In 2.x you can specify a timeout for WAIT transactions (isc_dpb_lock_timeout argument in the ODS 11+ API). But, even if you are using Fb 2.x on an ODS 11.x databases, it's not likely this is surfaced in any version of IBX. Considering the fervour with which IBX's maintainer Jeff Overcash refuses to implement support for Firebird improvements, I would love to be proven wrong. ;-)
./heLen