Deadlock on read?

[seven]

Hello all.

I have a method of a facade session bean (stateless) that only accesses (by reading) 2 entity beans instances (with pk1 and pk2, in this order). The same method, is some other situations (business requirements) accesses the same 2 entity beans instaces, but in the reverse order (pk2 and pk1 respectively). When to parallel clients call the facade method(client A calls with pk1,pk2 and client B calls pk2,pk1), I get a DEADLOCK.

My question is: are the entity beans locked within the tx started by the session bean method, even if the entity beans methods called are "get" methods? If so, how can I configure jboss in order NOT to lock the entity beans when read only methods ("get" methods) are called upon them?

I guess that if posible, the "get" methods should return not commited data of the entity bean.

Thanks.

[juha]

see the docu on read-only entities and CMP fields

[seven]

Unfortunately, the EB (entity beans) I was talking about don't have only read methody, they have update methods also, so I can't apply "read-only" attibutes on the entire bean.

I need to know If I can make only some of the methods of a EB not to wait until posibily other TXs that are locking the EB have finished.

And If u know a solution, It would be appeciated any examle.

Thanks again.

[juha]

yes you can, see Dain's CMP docu

[seven]

I tested in jboss-3.0.3 and the <read-only> tag at method level has no effect. This tag is not even in the jboss_3_0.dtd file. It seems that it's in jboss_3_1.dtd of jboss 3.2beta

See http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=forums/

[minamoto]

Did you try to set a transaction attribute other than required to your read-only method?
How about supports or nerver as a work around.

Miki