If your clients are all threads so you have a master process reading the
add/del sounds OK.
If you have to restart your client it sends a message to the master to send
all current jobs to you so you can crank off all the threads.
Then add/del works after that.
You'll want to think this through carefully...what happens if your producer
dies or a thread dies or all your threads die?

Also...how dynamic are your jobs?  E.g. Could you just have a pool of 50
consumers looking at 50 queues and the producer can just use whatever queues
it wants?
Then you wouldn't need to worry about add/del.

Are you in a client/server config or is this all being done on one machine?
Both producer and consumer?
If one machine I'd be tempted to use named pipes.

-----Original Message-----
From: SledgeHammer [mailto:[email protected]] 
Sent: Thursday, April 25, 2013 4:43 PM
To: [email protected]
Subject: RE: Is this possible with ActiveMQ?

Hmm... one queue for each producer...

Hmm... guess I would need a "System Queue" that gets "queue created" /
"queue deleted" notifications? that'll send the list of queues to the
clients? or is there some built in mechanism for that? Keep in mind I'm
using C# / NMS.




--
View this message in context:
http://activemq.2283324.n4.nabble.com/Is-this-possible-with-ActiveMQ-tp46662
19p4666225.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to