Just to give more information about the use case. The target ejb2 cmp bean method is performing a read-only batch operation on many rows in the database (get application user group membership list).
This method is marked with "@ejb.transaction type=NotSupported" and the bean has row-locking=true.
I'm thinking that the row-locking should be disabled for this case since there is no active transaction.
This is an edge case but I think its worth addressing. I'll Jira it and fix it if there is agreement that its safe to fix. I didn't want to Jira it if were not going to fix it.
In theory that sounds ok. But we do not recommend accessing entity beans w/o a transaction in our implementation. Some code relies on an active transaction.
I created JBAS-4433 to track this and noted that active transactions are recommended when accessing entity beans. JBAS-4433 is about ignoring the row-lock flag if there is no active transaction.