Perhaps I have misunderstood what you are proposing in that case :) The pool, as far as the client is concerned, should be a single entity but the internals are currently such that there is a single association between the connection and the sessions, whether XA or non XA. This client view should be retained but it would be better for the internals of the pool to manage the associations between the connections and their sessions independently, both for non-XA and XA resources. The 'client pool' would therefore contain a number of internal pools. Your second option sounds as if you intended to keep a single internal pool of the sessions but this would complicate the tracking of the relationships. Of course this may not be what you had intended. Perhaps you can give an expanded description of your options so that we can get a better understanding of what you are proposing. Kev Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230315#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...