How are you handling logins? Why are you calling getSession(), then invalidate() and getSession() again? Who is this "original guy" you mention, and what's the relationship with the person who just logged in?
Re: max number of sessions, assuming a sessions doesn't have a ton of data stored in it, the issue isn't really how many sessions, but how many requests are causing session replication. We've done some benchmarks where we handled ~ 450 requests per second on a 4 node cluster using REPL_SYNC. See http://jbento.oscj.net/httpsession2.html for details. The charts on that page show ~275 per sec, but we found that by driving the test fixture harder (shorter pause between requests) we could get ~ 450/s. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928062#3928062 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928062 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
