"timfox" wrote : I have seen this problem come up many times in different guises. | | What we're really talking about here is some kind of "sticky" thread pool executor. | | Where you have a pool of threads to service requests, but consecutive invocations can have an affinity for a particular thread depending on some key (this corresponds to the "session id"). | | I'm kind of surprised j2se doesn't already contain something that can do this. Yeah - well technically it doesn't have to be the same thread. The executor just has to guarantee that B "happens-after" A, in the same thread or a different one. I agree on the j2se statement (although it's really a trivial amount of code to implement; see the above link). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140654#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...