If you have on Queue per user login, and 1,000,000 users are concurrently connected to JMS, JBoss will at least create one socket and thread per queue. Depending on your operating system and your machine, it might be okay. Or might not work at all.
If you're writing such an application, the first thing I would be to do would write a test harness. Java historically has used the one-client-one-socket-one-thread processing model. The java.nio library allows you to write code that requires less threads. Theoretically, you could write a JMS system that used a thread processing pool that could handle a million JMS clients. This is not the design JBoss/JMS uses, however. If you go with a load-balanced, multi-node configuration, JBoss/JMS doesn't have true load balancing yet. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840810#3840810 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840810 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
