I just tracked this in the code - there seems to be no bug in this area. Threadsafe access to the keyset is garanteed by a ReadLock on the Node.
The Concurrentmodificationexception should only be thrown, if 'getChildrenNames()' and the iteration over the keySet are not done within the same transaction. Access to the keySet outside of a transaction is not garanteed to be threadsafe. Can you please check out whether this still happens with TransactionIsolationLever being set higher than 'NONE'? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3856661#3856661 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3856661 ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
