<div dir="ltr">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.<br><br>On Monday, July 15, 2013 7:40:11 PM UTC+1, Marcos Torres wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div><div><div>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.<br><br>Right now I'm working on a Windows Service and I need a way to listen on a queue all the time.<br>
<br>Here´s is the scenario:<br><br>Client A puts a message to a Queue (Q1)<br>Client B does the same thing to (Q1)<br><br>Service S listens to Q1 for incoming messages.<br><br><div>Something like this: <br>
<br></div><div>ClientA / ClientB => Q1 => { Service } <br></div><div><br></div><div>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? <br>
A push-based approach would be the ideal thing.<br></div><div>Doing some research, I saw something about the RequestedHeartbeat but No idea to use that. <br><br></div><div>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.<br>
<br></div>I'm using C# and the .NET client libraries.<br></div><br></div>Thanks in advance,<br></div>Marcos</blockquote></div>