You can declare an entity bean to use TX_NOT_SUPPORTED, and
with commit option B this effectively creates a read only cache. Even
if B is the not commit option you should be able to avoid the pessimistic
locking on the transaction. You have to be sure that this is the correct
semantics though.
>yes I'm getting a timeout at the app level. everything works fine with a
>single thread, no deadlock
>but as soon as I introduce two threads then deadlock happens everywhere.
the
>thing is that all of the methods are get( readonly)
>so why would I deadlock. why can't I just get my value from the entity bean
>and move on?
>
>or maybe it's the finders that are making all the fuss...
>
>-dom
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
