[rabbitmq-discuss] RPC style messaging with a clustered web application
benbennett at gmail.com
Thu Dec 2 14:35:04 GMT 2010
I am having the same issue. I was thinking each node would have its
own queue and in the message or something a routing key back to the
nodes queue, such that message could send a response back. Kinda like
a return address on letter.
On Thu, Dec 2, 2010 at 5:06 AM, Marek Majkowski <majek04 at gmail.com> wrote:
> On Thu, Dec 2, 2010 at 10:13, SimonT <simonthorogood at hotmail.com> wrote:
>> I think that we probably need a response queue per session created at
>> session start and some routing rules for the response messages based
>> on the session ID. However, I'm not clear on how these queues could be
>> expired once their purpose is complete? or if this is an issue?
>> (though I assume it is since we have many 100s sessions a minute).
>> There is no definitive 'end' to the session - currently it's
>> serialized state just expires after x amount of idle time.
> You should avoid having too many queues - they always consume
> some resources.
> Raw AMQP doesn't give any solution for this problem. Fortunately
> in RabbitMQ we have queue leases extension:
> What it does, is it tells the broker that the queue should be auto-deleted
> after a specified time of idleness.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss