Subject Re: [ib-support] dead locks no way out - URGENT - Not Fixed
Author Johannes Pretorius
Well how about the 4096 with the setting COMMIT RETAIN will that work
as we have the following problem

When they update record it hangs every now and again
there is about 10 people working. Also the deadlocks are becoming more and
more.

In the interbase log file I have a LOT of 10054 Socket Errors Server side
that says the host went down.

Can this endup in a dead lock for the others ??

Thanks in Advance
Johannes


At 10:52 28/11/2002 -0300, you wrote:
>In the jurassic period, when I used BDE, I think my settings was flag
>= 4608. It worked OK, considering the obvious BDE limitations.
>
>[]s
>
> Carlos
> WarmBoot Informatica - http://www.warmboot.com.br
> Interbase-BR - http://www.interbase-br.com
>
>JP> Good day
>JP> -\=\=-\=\=-\=
>
>JP> I have a problem with Interbase 5.6 where I keep on getting deadlocks
>with
>JP> Delphi 5
>JP> I have update the BDE to have the WAIT FOR LOCKS property and made it TRUE
>JP> also I made the driver flag 4096
>JP> But I keep on getting this error after a while
>JP> user transaction already in progress
>JP> update conflicts with concurrent update
>
>JP> PLEASE can somebofdy help
>
>JP> Johannes Pretorius
>
>JP> [Non-text portions of this message have been removed]
>
>
>
>JP> To unsubscribe from this group, send an email to:
>JP> ib-support-unsubscribe@egroups.com
>
>
>
>JP> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>To unsubscribe from this group, send an email to:
>ib-support-unsubscribe@egroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/