>I blame the server when it's vendor promises optimistic concurrency and
doesn't
>really provide it. You may be having problems with my statement because you
do
>not agree with the statement that deadlocks cannot occur with optimistic
>concurrency control. I don't care what actual products do that claim
optimistic
>concurrency, if they deadlock then the claims are false.
> --Victor
Do you agree that when two or more concurrent transactions update two or
more
resources without following a strict order, there's potential for deadlock?
If you do, then can you elaborate how optimistic concurrency can be deaklock
proof unless the container/resource manager has prior knowledge of the
application's execution plan.
Regards,
Hamid
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
