Hello Gerald,
> While following the recent "LOCKING-WAITING" threads I've been
> experimenting/tuning my beans for concurrency by turning reentrant on and
> setting TX_SUPPORTS. Great improvement!
Ah, at least one person giving it a try, thanks. I should have
done this on my own, but I'm just too busy reading and understanding
JBoss code (and really, I have more than enough work to do USING
JBoss and not trying to understand it in depth, my boss is very unhappy
with me the last days).
> However sql statements always rollback after the bean gets invoked
(creaters,
> finders, getters/setters anything) without a transaction context.
Oops, that again comes unexpected for finders and getters. Do you
have isModified() implemented in your beans? If not, would you
give it another try, implement isModified() and only access your
beans via finders and getters? Does the rollback show up then?
If so, would you please send stack traces to this list (or to me)?
My suggestion (no TX + reentrant) was really ONLY for pure readonly
access to beans, NEVER attempt to create, update or delete a bean
without a TX!
Thanks
Georg
___ ___
| + | |__ Georg Rehfeld Woltmanstr. 12 20097 Hamburg
|_|_\ |___ [EMAIL PROTECTED] +49 (40) 23 53 27 10
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
