> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of danch
> Sent: Tuesday, June 05, 2001 1:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Caching - Locking - Server Dies!
>
>
> Bill Burke wrote:
>
[snip]
> >
> > IMHO, there should be an option to remove EntityBean locking
> and let the
> > Database handle the synchronization either through the
> select-for-update
> > option, or doing the locks in BMP.
> >
>
> I'd tend to agree, but that we'd also have to allow multiple instances of
>
I thought the spec stated that an EntityBean could only process one request
at a time unless it was marked as reentrant?
> a bean in memory in order to gaurentee the proper threading
> behavior. This
Can you specify the "proper threading behavior" or point it out to me in the
spec? Thanks...
> would improve throughput on scenarios with small datasets and large
> numbers of concurrent users.
>
More importantly, IMHO, read-only beans would not lock, again improving
throughput and decreasing the likelyhood of deadlock. Plus, I find more
often than not in our application, we mostly don't care about EntityBean
synchronization. In our application, for instance, this locking is just
totally useless because we have multiple instances of JBoss on mulitple
machines hitting the DB. All the locking MUST be done within the DB.
I wonder how hard it would be to implement this? You'd have to write a
different InstanceInterceptor. What other stuff?
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
