Brian, We will have to try to get access to the StandardSessionFacade from there as well (perhaps through the ClusteredSession). anonymous wrote : | The concern I have is StandardSession.facade is not thread safe, and what's returned from getSession() needs to be if we are going to use it as a mutex. | We will only synchronize on the StandardSession.facade object and not modify it. Since we are not modifying the StandardSession.facade object, we do not need it to be thread safe. At least that is my thinking, let me know if I'm missing something :-) anonymous wrote : | There's no ref to facade outside StandardSession.getSession(), so ClusteredSession can override the getSession() method and replace the field with a volatile field and synchronize the construction if null. | I don't really understand the case when getSession would return null. I wonder if the null session case signify something special that needs to be preserved? For what its worth, the javadoc for Requests.getsession() is: /** | * Return the session associated with this Request, creating one if necessary. | */ | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240146#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...