ActiveMQ keeps open socket connection to all clients, as that's the nature of JMS communication.
Sure there's a limit in number of open sockets underlying system can take, that's where other scaling techniques (horizontal and hybrid) comes into play. You can also implement some kind of polling in your application and open/close JMS connections when you need them. Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net Connect at CamelOne <http://camelone.com/> May 24-26 The Open Source Integration Conference On Fri, Jun 3, 2011 at 4:41 PM, erickmelo <erickm...@gmail.com> wrote: > Hi Dejan, > > Thank you for the answer. The slides helped to understand how to scale > ActiveMQ.. But some questions remains: > - How ActiveMQ handle the subscribers of a non-persistent topic? Does it > consider all connected users at the same moment (with a tcp socket opened)? > Or is there some strategy for supporting Ajax clients (that uses a > pooling)? > > - On the slide 25 the problems of vertical scaling are listed... Thread > count is on of the main problems, but I think opened sockets are also a > problem... If ActiveMQ keep a opened socket with each client the OS limit > of > thread maybe a problem or not? > > I've an idea of using ActiveMQ to notify a large number of clients > subscribed to a topic at the same time (small control messages - > non-persistent). At this point I'm evaluating how much servers will be > needed to serve this task... > > Best Regards, > > Erick > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/How-ActiveMQ-handle-thousand-of-subscribers-in-a-Topic-tp3569320p3571030.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
