Re: optimistic locking and deadlock (was EBs are slow)

[James Cook]

From: "Rickard �berg" <[EMAIL PROTECTED]>

>> I guess you could elaborate on how option A works
>> in a clustered environment. Or is this also one of
>> those things where it *is possible*, but only with
>> a cluster that doesn't duplicate its beans in multiple
>> containers?

> There would be two ways I think:
> * dedicate each node to a particular entity -> no need
>   to update
> * Use a CMP implementation that does synched cluster
>   caching. Use, for example, timestamps for optimistic
>   concurrency control, or global locks for pessimistic CC

> The latter /w OCC would be the more likely case I guess.

The former precludes object failover, which is the primary reason for
clustering in the first place.

The latter requires so much overhead (and serialization) that any benefit
derived from Option A (entity caching in the container) is lost.

jim

===========================================================================
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".