Pete Beck wrote:
Dear JBoss gurus,I think you can declare "read-only" descriptors at method-level on jboss.xml. But AFAIK this feature is available only in JBoss-3.2.0.
I've noticed that JBoss aggressively locks beans in a pessimistic
locking strategy.
I've read that optimistic locking is on the way, which sounds like a
good thing.
The problem I've found with the current locking strategy is that it is
very easy to get deadlocks as the load on the system increases.
Judging by a lot of the posts on this list, I don't think I'm the only
one who has experienced this.
In EJB, it's possible to mark a bean as read-only. However, there
doesn't seem to be any sematics if you want to access a bean as
read-only only some of the time.
It seems that if it were possible to grab "read-only" locks on an EJB
then it would greatly reduce the problems of pessimistic locking.
An apropriate place to do this would be in finder methods, i.e. the
ability to mark a finder method as returning read-only instances.
Would this sort of feature be possible to implement in JBoss? Or is
there some flaw in my reasoning and I'm being hopelessly naive?
You can use this approach with QueuedPessimisticLock manager and commit option A and your EJB won't be locked while a tx executes a RO method.
regards,
horia
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
