Hi!
Ian McCallion wrote:
> Serial reuse of the same instance would adhere to the principle that there are
> never two threads executing in the same instance at the same time. It would be
> equivalent to use of pessimistic locking with exclusive locks even for read-only
> access so would be an unsatisfactory designpoint for a server. I suppose it may
> be a useful deployment option in some bizarre situations!
Now that was kinda harsh, since one of the most popular servers (i.e.
WLS) uses this approach. Would you, given your above opinion, say that
WLS sucks? ;-)
Do you think EntityBean caching between tx's would work in a
multi-instance implementation? What about the overhead for managing the
multiple instances?
As always, having the option is preferred. The largest drawback that I
can think of is high-volume read-only contention, but then again if
you're really high-volume one would use several server instances, which
in effect means a multi-instance scenario (unless a cluster-wide
pessimistic lock is acquired..phew).
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
