In our setup we are using HTTP session clustering to cluster the stub to a clustered stateful session bean... all works great except for one thing. Our infrastructure guys cant guarantee stickiness to a particular app server so it appears that what is happening is when a web user flicks across to the other app server, the replicated stub in the HTTP session chooses to go back to the original application server rather than choose the stateful session in the same VM. Is this normal behaviour? and is there anyway to have the stub choose the session bean in the local VM?
A priori, this is not the expected behaviour: local deployment is always favoured.