> That is actually what I did in the reverted changes. Not saying all the changes you made were completely wrong? the revert was simply back to the way it was before (working) until a more stable solution was found - which is what we are doing right? If I put your changes back 'as is' in then then it does not work any more for whatever reason. I.e I cannot redeploy an application any more.
The ConcurrentModifiedException was preventing the actual JarFile from being removed or closed even after 5 iterations and files remained locked. If you want to modify your code taking into account that 'remove' on either of the maps is likely to throw a Throwable at least once during any iteration and put it back then would be great :-) -- View this message in context: http://openejb.979440.n4.nabble.com/Re-svn-commit-r1146747-openejb-trunk-openejb3-container-openejb-core-src-main-java-org-apache-openeja-tp3674308p3680114.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
