After much searching I think I found my problem. Does this make sense to you.. I do not specify a isolation level in my service.xml, so (I think) I use the "LockStategyNone".
When I have 2 threads doing a repeated add/removes on the same node. One does not wait on the other, and the adds and deletes are inter-mingled. So in the nodeEvent queue, I get an add/add/delete/delete. Then when the eviction alogrithm starts to process the queue, it processes an add, then another add (which does not do anything, because it is already in the map), then a delete and then the second delete fails. a few questions.. 1) Is this a reasonable explanation of what is going on? 2) Does the default LockStragety make sense, should it ever be used? should the default change? 3) Does the eviction policy need changing to accomodate this (allow multiple entries in the map, or ignore the error, or ??) I can send trace level logs if you want, but they are too large to post here. Thanks -Kevin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872639#3872639 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872639 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
