On Mon, Apr 8, 2013 at 4:05 AM, Anton Piatek1 <anton.pia...@uk.ibm.com>wrote:
> > > Multiple tabs/windows is one thing, but multiple clients are just as big a > problem. > Not a problem or a concern in my web app. Endusers are trained to use the web app in 'one' browser tab/window 'per device'; every now and then, I can tell when they have accidentally opened more than one browser tab/window while using the web app. Still, not a 'big' problem or concern to 'me'. Hmmm interesting, a thought just came to me on some code I can write/add to possibly prevent user from opening multiple browser tab/windows per device (or ip address). Thanks for the motivation. :) > > Have you looked at how many tomcat threads you have running and what > happens to each of them as you open more websockets? What if you open more > websockets than you have threads... > I open one websocket per client (client = user-login-per-device), and the app pushes messages to the logged-in users. Currently, my web app is used by a small number of users on the different devices that they use/own, and I have no need to limit the # of threads to the # of potential users; accepting the default # of threads has allowed my web app to work well on Windows Server 2003 32bit server (initial/previous production server), and now, on windows 2008 64bit server (current production server). I understand that you want to test/prepare for worst-case-scenario.
