I am implementing a queue that is part of the tree cache. Each request will come in and pick the next available work from the queue, and remove that work item from the queue. The queue is shared across the cluster via the tree cache. If the transaction locking is only limited to the tree on which the txn (in this case, read and remove) occurs, then will I not have a problem with multiple requests on different servers picking up the same item (when one server has picked an item, and then removes it, but another server comes in before the txn is completed and the remove is replicated)? Do you have any suggestions on how to handle this scenario?
Thanks, Abitha. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871379#3871379 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871379 ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
