Hello Sudhir
"You better keep your transactions short or else I may not guarantee a complete lock for ya"
I do not have an answer for this, but it seems very irresponible if the container have this attitude
It seems to be no point in keeping the transaction open if it doesn't keep the lock on the row. Maybe this just gives the container the oppertunity to remove the bean from memory while more active beans need it more, but at the same time keep the transaction open and the row locked.
This is just a more or less educated guess...
/Magnus