row-locking would help. But it might not be the best option in your case.

Phil Shrimpton wrote:

On Tuesday 18 November 2003 14:58, Alexey Loubyansky wrote:

Hi,


Are the clients accessing different orders which have common items? And
then one of the common items is removed?

Yes, they could also be accessing the same 'order' and (with the same the same items)

Then the problem might occur when clients access *different* orders which share items. The call order.getItems() can be performed at the same time for both clients (w/o locking) as orders are different. But when a shared item is removed by one of the clients, it is still in the other's client collection.


This sounds like my problem. Whats the best way to prevent/detect/workaround the issue

Phil




-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to