activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Temp queue vs topic via message selector?
Date Fri, 31 Aug 2007 21:40:32 GMT

Hi all,
We are currently using temp queues for dispatching data to a number of
clients. In this way each client gets only his own data, request response
style. However we are having lots of trouble with the temp queues and the
broker blocking. We also have topics to dispatch updates to all clients,
which are working well. Instead of a temp quueue for each client, we are
considering using just one permanent topic onto which we would send all
client response data, with each client using a unique message selector to
only get his data. What do ye think of this approach, does it make any
sense? We are worried that the throughput could drop off with all data being
published onto the one destination rather than distributed across many(would
each clients interfere its each others throughput), but we are hoping our
blocking issues would be solved.

Any opinions or pointer would be appreciated

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message