findByPrimaryKey and locking

[frintrop]

hy,

i have configured one entity to use row locking / select for update.
why jboss 3.2.5 generates no SELECT FOR UPDATE if is use findByPrimaryKey.

findAll will use SELECT FOR UPDATE ....

[aloubyansky]

How do you configure it?

[frintrop]

we are using xdoclet and middlegen to generate our entities.

added this xdoclet tag to the entity:

*@jboss.persistence
* row-locking="true"

[aloubyansky]

It works for 3.2.6. I don't remember any issues/changes wrt row-locking. I'll test with 3.2.5 this weekend.

[ikigovenku]

I am also having the simillor problem. Previously i am using 3.2.1 and used <row-locking>true</row-locking> for entity level. I just upgraded to 3.2.5 and it is giving following oracle exception.

Error = Find failed: java.sql.SQLException: ORA-01786: FOR UPDATE of this query expression is not allowed

From the forum i found that findAll, DISTINCT etc... QL's will not work for row locking "true". But I want use rowlocking for findByPrimaryKey method. Please let me know how to configure it.

Thanks in Advance

-Venku

[aloubyansky]

row-locking works in 3.2.5. Nothing has changed.
You can't use distinct and FOR UPDATE (it's not a JBoss-specific limitation).

[ikigovenku]

Alex,

How come in 3.2.1 <row-locking>true</row-locking> is working with DISTINCT and causing problem in 3.2.5. FYI I haven't changed the DB.

-Venku

[ikigovenku]

any ideas?

[aloubyansky]

All jboss does if row-locking is true is just adds FOR UPDATE (or another sb-specific template) to SELECT. Everything else is db/driver's responsibility.

[oyabun]

All jboss does if row-locking is true is just adds FOR UPDATE (or another sb-specific template) to SELECT. Everything else is db/driver's responsibility.

It doesn't add FOR UPDATE to findByPrimaryKey()... even though it doesn't use DISTINCT. It looks like findByPrimaryKey() doesn't use the row locking template, which ist bad IMO.