Will the current concurrentSessionController implementation work in a clustered environment?
I see that it uses in-memory collections to store lists of sessions & their related principals, so these lists are local to one app server instance (jvm).
Would it be necessary to add a DAO-based implementation of these lists to provide enforcement of a concurrent login policy across members of a cluster?


