[JBoss-user] commit-option per bean?

[Glenn Lewis]

Hi All,

Setup: Jboss 3.0.3 with CMP, Postgres 7.

One of our session beans selects an entity bean instance deletes that instance from the table. Problem was that two clients could concurrently select the same instance and one would delete it, leaving the other with an invalid instance. This happened even if the select and delete was done inside a user transaction.

We didn't want to change the transaction isolation level from READ_COMMITTED just for this problem, so instead the session bean now calls a postgres function that does the select and delete in one step.

This solves the first (concurrency) problem, but because the changes are not made through the beans, the jboss cache is no longer valid. This can be solved by setting the commit-option to level C (from B), but that means all beans are at level C.

Is there a way to set the commit-option per bean, or a better way to solve our orginal problem?

Any help very much appreciated!

thanks

--
Glenn



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user