Have been working on a pilot project to use ActiveMQ as core message provider for a legacy system (which is C++ based)
One of the critical requirement is to figure out the best approach to solve following problem 1. I have ESB converting the WS/SOAP callouts into JMS endpoint and pushing the messages into ActiveMQ container. 2. Have CMS handlers on the C++ side to consume/pick the message and reply back. What is not clear to me is, 1. Can i have 2 different operations of a service push the messages to same queue? (e.g. Authentication service has login and logout operation). What is the best approach for these scenarios? How would the scalability issue play into this, assuming there would be 100 users using the system simultaneously? 2. Do i need to create CMS handlers as .exe files. Coz, that way, i would end up having n number of CMS handlers ( .exe files) as consumers for each of the services? Is there a best approach for solving this? 3. How is multi-threading handled by the ActiveMQ CMS apis? thanks in advance.. -- View this message in context: http://www.nabble.com/Urgent%3A-ActiveMQ-CMS-multi-handlers--tp20890368p20890368.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
