Subject | Re: [IBO] deadlock error on IBO /FB 1.02 - what may be the reason ? |
---|---|
Author | Aage Johansen |
Post date | 2003-12-04T20:56:30Z |
On Thu, 4 Dec 2003 16:46:49 +0000 (UTC), bjorgeitteno wrote:
Can you update+commit the record from another app (e.g. IB_SQL) after
closing the first app (before closing the second)?
--
Aage J.
> ...I get
>> ...
>>> The error:
>>> When I start 2 instances of this application with the same user name,
>>> the "deadlock" error when closing app nr. 2. No matter if it was startedHi Bjørge!
>>> first or last. I am fairly sure all writings to table USER_SETTINGS is
>>> committed immediately.
>>
>> How do you verify that the commit occurs? Are you *really* calling Close
>> on the transaction instead of a hard commit?
>
> No. I call a Commit;. and I've been able to track execution into the
> xxx.IMP file. I do not call 'Close'. An explicitly started transaction.
>
>>> I know the problem is within writing the last table, because the error
>>> doesn't appear if I write to another record here.
Can you update+commit the record from another app (e.g. IB_SQL) after
closing the first app (before closing the second)?
--
Aage J.