> with networks of brokers anyway - but to reduce the number of
> threads in use do the following:
>
> 1. reduce number of threads for connections in the broker use NIO
> 2. Use optimizeDispatch in the Queues
Thanks Rob, but neither of these reduced the number of threads. With NIO the
thread name
> What about using selective consumers? That way one queue can act like
multiple queues.
Okay, so how does ActiveMQ deal with a single queue, 6000 consumers, and
6000 different selectors?
> reduce number of threads for connections in the broker use NIO -
I've found next to no information on
Hi,
I'm designing a system that will have a few central services and upward of
6000 processes on thousands of machines on a LAN. They all communicate using
ActiveMQ, with the central services having well-known queue names and the
distributed components having randomly-generated queue names. I rec
