Thanks for you quick response. Just to understand your answer, Does every consumer that has been configured work on one message at a time, or does the dispatcher kick off a new consumer for every message it has?
So lets say I have 100 messages in a queue and a single consumer configured. Would there be a single consumer that works on one message at a time, or would the the dispatcher try to kick off 100 separate consumers. Then lets say I wanted to have 5 messages worked on at a time. Would I need to configure 5 separate consumers, or would I do that through the dispatcher throttling? One more question, is there any documentation on the dispatcher throttling? Thanks again for helping out a newbie. -Kevin bsnyder wrote: > > On Jan 24, 2008 10:38 AM, Kevin k <[EMAIL PROTECTED]> wrote: >> >> A quick question or 2 about jms providers: >> Lets say a jms queue has many,many messages in it (messages going in >> quicker >> than being processed) >> >> 1) how many messages are worked on at one, or to ask it another way how >> many threads does the jms provider kick off by default? > > It's not matter of threading in the broker as much as it's a matter > how how fast the consumer is and how many consumers there are. > Threading in the broker will certainly affect how quickly messages are > delivered to any consumer, but if that consumer can't keep up with the > message dispatching then you need to etiher throttle the dispatching, > add more consumers or both. > >> 2) Is this number changeable? >> 3) Assuming we have activeMQ setup correctly (load balanced, master >> slave, >> anything else?), is there any problems running several the identical jms >> provider on different servicemixes to get load balancing. > > As long as you have the same SAs deployed on each instance of > ServiceMix and the underlying ActiveMQ instances are set up in a > network of brokers > (http://activemq.apache.org/networks-of-brokers.html) if/when one of > the instances crashes, the messages will be load balanced. Setting up > this type of environment requires a lot of testing because there are > many possible configurations for ActiveMQ as you began to point out by > mentioning master/slave, etc. > > Are you experiencing some type of issue? If you are having a problem > then we should discuss that problem specifically. It's always better > to talk about a concrete problem that *is* happening instead of > talking at such a high level about how things *should* work. > > Bruce > -- > perl -e 'print > unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" > );' > > Apache ActiveMQ - http://activemq.org/ > Apache Camel - http://activemq.org/camel/ > Apache ServiceMix - http://servicemix.org/ > Apache Geronimo - http://geronimo.apache.org/ > > Blog: http://bruceblog.org/ > > -- View this message in context: http://www.nabble.com/jms-limiting-tp15070635s12049p15072288.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
