[rabbitmq-discuss] Question about long-lived connections

[josh]

There is a default heartbeat negotiated between the client and the server. 
I think this is since version 3.0 but may be wrong. I guess it's value 
depends on the setup. For our Java/OSX/RHEL setup over a Gb LAN it seems to 
default to 30 minutes. We're using a load balancer in the middle though and 
this times out TCP connections after 1 minute of inactivity. We simply set 
the heartbeat to 30 seconds on the ConnectionFactory and everything stays 
alive indefinitely. Certainly many days even if there is no application 
activity.

On Monday, July 15, 2013 7:40:11 PM UTC+1, Marcos Torres wrote:
>
> First of all, I'm doing my first project with RabbitMQ and I'm very happy 
> with the results so far, so, good jobs guys.
>
> Right now I'm working on a Windows Service and I need a way to listen on a 
> queue all the time.
>
> Here´s is the scenario:
>
> Client A puts a message to a Queue (Q1)
> Client B does the same thing to (Q1)
>
> Service S listens to Q1 for incoming messages.
>
> Something like this: 
>
> ClientA / ClientB => Q1  => { Service } 
>
> So far I was thinking in the EventingBasicConsumer on the Service side, 
> but I'm not sure about the underlying connection. Is there a time out I 
> need to be aware of? 
> A push-based approach would be the ideal thing.
> Doing some research, I saw something about the RequestedHeartbeat but No 
> idea to use that. 
>
> Also, I know there is the Shovel plug-in but not sure if it fits in this 
> scenario because I still need to face the consume of the Q1 queue, that´s 
> the real issue.
>
> I'm using C# and the .NET client libraries.
>
> Thanks in advance,
> Marcos

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130926/f353f959/attachment.htm>