Would inserting a timer of 0 duration do the trick? It's ugly, too, of course. I'm wondering if this problem is peculiar to process creation, or if a similar race condition can happen later on an update as well. Hopefully, a row-lock in the database prevents undesired concurrency - but I don't know whether that's actually done, and which databases it works on. Does anyone know? -Ed Staub View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008454#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...