Hi Ingo,
There is no automatic time-out mechanism in J2EE that you could
adapt for use in a pessimistic locking scheme. One possibility
might be to store leasing information along with check-out
information. When a conflicting client tries to obtain a lock, the
existing lease could be examined for validity.
I'm not sure what you mean by using stateful session beans to
organize entity beans like leased resources.
-Dan
P.S. I probably should have mentioned before that optimistic
locking is generally a more favorable approach except in situations
where the optimism is unjustified--i.e. high contention for the same
data; or in situations where backing out a transaction has high
costs--e.g. a lot of work is done during "client think time."
On 18 Oct 00, at 19:51, Ingo Bruell wrote:
> Hi Dan,
>
> Wednesday, October 18, 2000, 5:02:41 PM, you wrote:
>
> DO> Hope this helps,
>
> Yes, thank you. Is there a mechanism, that if I store that a client is
> using the EntityBean, to clear this state after a timeout ?
>
> Or should I use Stateful SessionBeans, which organize the use of the
> EntityBeans like LeasedResources ?
>
>
> so long
>
>
> Ingo Bruell
>
> ---
> <[EMAIL PROTECTED]>
> <ICQ# 40377720>
> Oldenburg PGP-Fingerprint: 9DD0 1776 DF4D 5B16 A532 C2A1 4701 EEA2
> Germany PGP-Public-Key available at pgpkeys.mit.edu
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
