Subject | Re: [ib-support] Concurrent API calls into gds32 cause lock |
---|---|
Author | Claudio Valderrama C. |
Post date | 2002-04-02T01:29:53Z |
""nitaligavino"" <Dan.Crea@...> wrote in message
news:a89u7q+5553@......
stablish a different connection to the engine.
preventing effective garbage collection in the long time (although with Read
Committed it's not as bad) but it has no direct impact in deadlocks.
C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing
news:a89u7q+5553@......
>The local protocol is not multi-client rfiendly. Also, every thread should
> This is but one of the issues that I have seen but overall it's the
> same for all my deadlocks. So I found some information that said
> that this can be prevented by using TCP/IP as the connection.
stablish a different connection to the engine.
> Thus: "localhost:c:/test.gdb". However, I also read that the issueCommit Retaining does a commit and keeps the context of the txn, thus
> is in the commit retaining call?
preventing effective garbage collection in the long time (although with Read
Committed it's not as bad) but it has no direct impact in deadlocks.
> Finally, I read that using theWhere did you read that crap?
> TCP/IP call is not safe on dialect 3, IB 6?
C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing