"david.lloyd(a)jboss.com" wrote : | As far as using a concurrent queue - perhaps you could squeeze out a tiny bit more performance, but unless it shows up as a blip on a profiler, I'm not going to bother because frankly I doubt that there will be significant (unwanted) contention for the lock. (Remember that the purpose is to serialize access, after all) After profiling JBM, this actually appears as the single largest point of contention in the application (the second being the MINA DefaultIOSessiondataStructureFactory) contributing to about 12% performance degradation when sending / consuming a lot of messages. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150439#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...