not sure what you are asking exactly, but if you are worried about the scalability of topics, then just use a single topic and either a http://camel.apache.org/content-based-router.html content based router or http://activemq.apache.org/selectors.html AMQ message selectors ...
otherwise, http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html here are some notes on handling large number of threads/file descriptors if you go that route... johnston73 wrote: > > Hi > > Appreciate your suggestions on my design of routes below. Suppose I have > a scenario: > > I have An processes talking to multiple services Bm using message > publish/subscribe pattern. > > A1...An <----bus------> B1...Bm > > I design my routes as follows: > > R1: from("topic:B1.*") to("A1") > R2: from("topic:A1*") to ("B1") > R3: from("topic:B2*") to ("A1").. > ... > Rn(2) > > So my question is: Do I need that my topics to take care this scenario? > In addition, each topic would open one TCP connection. Imagine that > eventually i will run out of file descriptors > > Thanks > ----- Ben O'Day IT Consultant -http://consulting-notes.com -- View this message in context: http://camel.465427.n5.nabble.com/Route-question-tp4946967p4956560.html Sent from the Camel - Users mailing list archive at Nabble.com.
