<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <meta name="generator" content="Osso Notes">
    <title></title></head>
<body>
<p>Mj----- Original message -----
<br>&gt; Send rabbitmq-discuss mailing list submissions to
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<br>&gt; 
<br>&gt; To subscribe or unsubscribe via the World Wide Web, visit
<br>&gt; 
<br>&gt; <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a>
<br>&gt; or, via email, send a message with subject or body 'help' to
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  <a href="mailto:rabbitmq-discuss-request@lists.rabbitmq.com">rabbitmq-discuss-request@lists.rabbitmq.com</a>
<br>&gt; 
<br>&gt; You can reach the person managing the list at
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  <a href="mailto:rabbitmq-discuss-owner@lists.rabbitmq.com">rabbitmq-discuss-owner@lists.rabbitmq.com</a>
<br>&gt; 
<br>&gt; When replying, please edit your Subject line so it is more specific
<br>&gt; than &quot;Re: Contents of rabbitmq-discuss digest...&quot;
<br>&gt; 
<br>&gt; 
<br>&gt; Today's Topics:
<br>&gt; 
<br>&gt;&nbsp; &nbsp; &nbsp;  1. Re: Installing RabbitMQ STOMP for PyGoWave (Simon MacMullen)
<br>&gt;&nbsp; &nbsp; &nbsp;  2. Re: RabbitMQ for Master worker with monitoring? (yoav glazner)
<br>&gt;&nbsp; &nbsp; &nbsp;  3. Re: RabbitMQ for Master worker with monitoring? (Emile Joubert)
<br>&gt;&nbsp; &nbsp; &nbsp;  4. Re: Question about Connections and Channels (Thadeu Russo)
<br>&gt;&nbsp; &nbsp; &nbsp;  5. Re: Installing RabbitMQ STOMP for PyGoWave (Chris)
<br>&gt;&nbsp; &nbsp; &nbsp;  6. Re: RabbitMQ for Master worker with monitoring? (yoav glazner)
<br>&gt; 
<br>&gt; 
<br>&gt; ----------------------------------------------------------------------
<br>&gt; 
<br>&gt; Message: 1
<br>&gt; Date: Thu, 23 Dec 2010 12:52:30 &#43;0000
<br>&gt; From: Simon MacMullen &lt;<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>&gt;
<br>&gt; Subject: Re: [rabbitmq-discuss] Installing RabbitMQ STOMP for PyGoWave
<br>&gt; To: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<br>&gt; Message-ID: &lt;<a href="mailto:4D13460E.30706@rabbitmq.com">4D13460E.30706@rabbitmq.com</a>&gt;
<br>&gt; Content-Type: text/plain; charset=ISO-8859-1; format=flowed
<br>&gt; 
<br>&gt; On 23/12/2010 6:16AM, Chris wrote:
<br>&gt; &gt; Also, I forgot to mention that I've upgraded to RabbitMQ 2.2.0.
<br>&gt; 
<br>&gt; In that case it will almost certainly be simplest to download the
<br>&gt; plugin 
<br>&gt; as a binary from <a href="http://www.rabbitmq.com/plugins.html">http://www.rabbitmq.com/plugins.html</a>
<br>&gt; 
<br>&gt; (NB: plugins tend to be very version-specific, and do not work at all 
<br>&gt; with 1.6.0.)
<br>&gt; 
<br>&gt; Cheers, Simon
<br>&gt; 
<br>&gt; 
<br>&gt; ------------------------------
<br>&gt; 
<br>&gt; Message: 2
<br>&gt; Date: Thu, 23 Dec 2010 15:25:42 &#43;0200
<br>&gt; From: yoav glazner &lt;<a href="mailto:yoavglazner@gmail.com">yoavglazner@gmail.com</a>&gt;
<br>&gt; Subject: Re: [rabbitmq-discuss] RabbitMQ for Master worker with
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  monitoring?
<br>&gt; To: rabbitmq-discuss &lt;<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>&gt;
<br>&gt; Message-ID:
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &lt;<a href="mailto:AANLkTimn9Fb2jvKszKORiEL-1j2OebohXgCZoLAhO-QF@mail.gmail.com">AANLkTimn9Fb2jvKszKORiEL-1j2OebohXgCZoLAhO-QF@mail.gmail.com</a>&gt;
<br>&gt; Content-Type: text/plain; charset=&quot;iso-8859-1&quot;
<br>&gt; 
<br>&gt; On Thu, Dec 23, 2010 at 12:26 PM, Emile Joubert &lt;<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>&gt;
<br>&gt; wrote:
<br>&gt; 
<br>&gt; &gt; 
<br>&gt; &gt; Hi Yoav
<br>&gt; &gt; 
<br>&gt; &gt; 
<br>&gt; &gt; On 22/12/10 20:24, yoav glazner wrote:
<br>&gt; &gt; 
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; On Wed, Dec 22, 2010 at 2:10 PM, Emile Joubert &lt;<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>
<br>&gt; &gt; &gt; &lt;<a href="mailto:emile@rabbitmq.com">mailto:emile@rabbitmq.com</a>&gt;&gt; wrote:
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; Hi Yoav,
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; On 21/12/10 21:35, yoav glazner wrote:
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; This is my first post to this list, so Hi!
<br>&gt; &gt; &gt; I'm trying to design a Master/Worker implement-ion with
<br>&gt; RabbitMQ.
<br>&gt; &gt; &gt; I have a few requierments due to lagacy issues:
<br>&gt; &gt; &gt; * works get very long tasks so they should be able to get
<br>&gt; ABORT
<br>&gt; &gt; &gt; messages
<br>&gt; &gt; &gt; while working,
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; You could send updated status information about work items to a
<br>&gt; &gt; &gt; dedicated status exchange that workers subscribe to in order to
<br>&gt; &gt; &gt; obtain abort messages or changes in priority. This assumes that
<br>&gt; &gt; &gt; tasks are interruptible and that workers have multiple threads of
<br>&gt; &gt; &gt; control.
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; that's good
<br>&gt; &gt; &gt; 
<br>&gt; &gt; 
<br>&gt; &gt; It sounds like you want to be able to communicate two different things
<br>&gt; to
<br>&gt; &gt; workers:
<br>&gt; &gt; 
<br>&gt; &gt; 1. tasks
<br>&gt; &gt; 2. task status updates
<br>&gt; &gt; 
<br>&gt; &gt; The updates (abort, reprioritise, pause) to tasks are the difficult
<br>&gt; part
<br>&gt; &gt; and the reason why frameworks like Celery won't work. I suggest you
<br>&gt; &gt; communicate task status updates to workers via a different route from
<br>&gt; the
<br>&gt; &gt; way you submit tasks. Translating that to AMQP means using using a
<br>&gt; separate
<br>&gt; &gt; exchange and queues, so workers accept tasks via a relatively
<br>&gt; slow-moving
<br>&gt; &gt; queue and obtain updates about task status via a different queue. This
<br>&gt; &gt; assumes that workers have more than one thread of control for
<br>&gt; listening on
<br>&gt; &gt; multiple queues and know how to interrupt running tasks. There may be
<br>&gt; lots
<br>&gt; &gt; of other ways of accomplishing your goal.
<br>&gt; 
<br>&gt; 
<br>&gt; But then I'll lose messages when a worker die, no?
<br>&gt; -------------- next part --------------
<br>&gt; An HTML attachment was scrubbed...
<br>&gt; URL:
<br>&gt; &lt;<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101223/e36507ce/attachment-0001.htm&gt;">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101223/e36507ce/attachment-0001.htm&gt;</a>;
<br>&gt; 
<br>&gt; ------------------------------
<br>&gt; 
<br>&gt; Message: 3
<br>&gt; Date: Thu, 23 Dec 2010 13:35:09 &#43;0000
<br>&gt; From: Emile Joubert &lt;<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>&gt;
<br>&gt; Subject: Re: [rabbitmq-discuss] RabbitMQ for Master worker with
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  monitoring?
<br>&gt; To: yoav glazner &lt;<a href="mailto:yoavglazner@gmail.com">yoavglazner@gmail.com</a>&gt;
<br>&gt; Cc: rabbitmq-discuss &lt;<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>&gt;
<br>&gt; Message-ID: &lt;<a href="mailto:4D13500D.5080807@rabbitmq.com">4D13500D.5080807@rabbitmq.com</a>&gt;
<br>&gt; Content-Type: text/plain; charset=ISO-8859-1; format=flowed
<br>&gt; 
<br>&gt; Hi Yoav
<br>&gt; 
<br>&gt; On 23/12/10 13:25, yoav glazner wrote:
<br>&gt; &gt; 
<br>&gt; &gt; But then I'll lose messages when a worker die, no?
<br>&gt; 
<br>&gt; Acknowledging messages only after successful processing will prevent 
<br>&gt; them from being lost in case the consumer dies. If a consumer dies 
<br>&gt; unacknowledged messages will be requeued.
<br>&gt; 
<br>&gt; Regards
<br>&gt; 
<br>&gt; Emile
<br>&gt; 
<br>&gt; 
<br>&gt; ------------------------------
<br>&gt; 
<br>&gt; Message: 4
<br>&gt; Date: Thu, 23 Dec 2010 11:51:29 -0200
<br>&gt; From: Thadeu Russo &lt;<a href="mailto:thadeurc@gmail.com">thadeurc@gmail.com</a>&gt;
<br>&gt; Subject: Re: [rabbitmq-discuss] Question about Connections and
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  Channels
<br>&gt; To: Emile Joubert &lt;<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>&gt;
<br>&gt; Cc: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<br>&gt; Message-ID:
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &lt;<a href="mailto:AANLkTikOoXywKt8SGGNkZSDeMPRQucHAinNhr9U1e1m1@mail.gmail.com">AANLkTikOoXywKt8SGGNkZSDeMPRQucHAinNhr9U1e1m1@mail.gmail.com</a>&gt;
<br>&gt; Content-Type: text/plain; charset=&quot;iso-8859-1&quot;
<br>&gt; 
<br>&gt; Hi Emilie,
<br>&gt; 
<br>&gt; thanks a lot for your comments.
<br>&gt; 
<br>&gt; One thing you pointed out called my attention:
<br>&gt; 
<br>&gt; &quot;I would expect it to be more convenient for you to have an AMQP client
<br>&gt; in
<br>&gt; each JVM and therefore use a connection per JVM. AMQP connections are
<br>&gt; cheap
<br>&gt; resources and you need not try to conserve them. Brokers with tens of
<br>&gt; thousands of connections are not unheard of.&quot;
<br>&gt; 
<br>&gt; This is the way I started implementing, and in each JVM I can have
<br>&gt; multiple
<br>&gt; consumers and producer, so I was thinking about have 1 connection per
<br>&gt; JVM
<br>&gt; with one channel per producer/consumer. I like the idea of separate
<br>&gt; producers and consumers.
<br>&gt; 
<br>&gt; As the project goes, I will update the list with question/comments.
<br>&gt; 
<br>&gt; Best Regards,
<br>&gt; 
<br>&gt; On Wed, Dec 22, 2010 at 3:41 PM, Emile Joubert &lt;<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>&gt;
<br>&gt; wrote:
<br>&gt; 
<br>&gt; &gt; 
<br>&gt; &gt; Hi Thadeu,
<br>&gt; &gt; 
<br>&gt; &gt; Your project sounds interesting. If I understand your question
<br>&gt; correctly
<br>&gt; &gt; you want to know if you should be using one connection with many
<br>&gt; channels,
<br>&gt; &gt; or many connections each with a single channel.
<br>&gt; &gt; 
<br>&gt; &gt; A possibly relevant consideration is that if the broker needs to apply
<br>&gt; &gt; backpressure because of an overactive producer then all the channels
<br>&gt; sharing
<br>&gt; &gt; a connection with that producer will be blocked. Channels that can't
<br>&gt; &gt; tolerate this risk should have a connection to themselves. For the
<br>&gt; same
<br>&gt; &gt; reason you may want to separate producers and consumers to use
<br>&gt; different
<br>&gt; &gt; connections.
<br>&gt; &gt; 
<br>&gt; &gt; I would expect it to be more convenient for you to have an AMQP client
<br>&gt; in
<br>&gt; &gt; each JVM and therefore use a connection per JVM. AMQP connections are
<br>&gt; cheap
<br>&gt; &gt; resources and you need not try to conserve them. Brokers with tens of
<br>&gt; &gt; thousands of connections are not unheard of.
<br>&gt; &gt; 
<br>&gt; &gt; 
<br>&gt; &gt; On 19/12/10 13:20, Thadeu Russo wrote:
<br>&gt; &gt; 
<br>&gt; &gt; &gt; Hi,
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; I need to architect a Java application using rabbitmq as its message
<br>&gt; &gt; &gt; broker. It is a distributed application and the message broker will
<br>&gt; play
<br>&gt; &gt; &gt; the role of connect the JVMs. Basically, each JVM has sets of objects
<br>&gt; &gt; &gt; (currently they are grouped by host:port) that can change messages to
<br>&gt; &gt; &gt; other objects in other groups in other virtual machines (there is a
<br>&gt; 1:1
<br>&gt; &gt; &gt; bi-directional relationship between groups of objects in different
<br>&gt; JVMs).
<br>&gt; &gt; &gt; The idea of use the broker is to avoid the number of tcp ports I have
<br>&gt; to
<br>&gt; &gt; &gt; open and also to take advantage of the message delivery guaranties.
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; The design is simple: each group of objects will have an exchange and
<br>&gt; 2
<br>&gt; &gt; &gt; queues (incoming and outcoming) to change messages.
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; I would like to know if you guys advise the following configuration
<br>&gt; &gt; &gt; regarding rabbitmq:
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; 1- Have 1 connection per JVM
<br>&gt; &gt; &gt; 2- Have multiple channels to that connection. Each channel will be
<br>&gt; &gt; &gt; associated with those 2 queues
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; What is concerning me is: the number of sends/receives per channel is
<br>&gt; &gt; &gt; high (about 5k/second). Should I have multiple connections (like a
<br>&gt; &gt; &gt; pool), or it is ok to use just 1 connection? If I have a pool of
<br>&gt; &gt; &gt; connections, I understand they will share the same tcp port, and I
<br>&gt; could
<br>&gt; &gt; &gt; not see any difference in using a single Connection.
<br>&gt; &gt; &gt; 
<br>&gt; &gt; 
<br>&gt; &gt; The broker port will be same for each of multiple connections, but the
<br>&gt; peer
<br>&gt; &gt; port will typically be random. The difference is that connections with
<br>&gt; a
<br>&gt; &gt; single channel can fail and block without affecting other connections.
<br>&gt; &gt; 
<br>&gt; &gt; Regards
<br>&gt; &gt; 
<br>&gt; &gt; Emile
<br>&gt; &gt; 
<br>&gt; 
<br>&gt; 
<br>&gt; 
<br>&gt; -- 
<br>&gt; Thadeu de Russo e Carmo
<br>&gt; <a href="http://www.thadeu.com.br/">http://www.thadeu.com.br/</a>
<br>&gt; <a href="http://www.caelum.com.br/">http://www.caelum.com.br/</a>
<br>&gt; <a href="http://www.caelumobjects.com/">http://www.caelumobjects.com/</a>
<br>&gt; -------------- next part --------------
<br>&gt; An HTML attachment was scrubbed...
<br>&gt; URL:
<br>&gt; &lt;<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101223/78c8d840/attachment-0001.htm&gt;">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101223/78c8d840/attachment-0001.htm&gt;</a>;
<br>&gt; 
<br>&gt; ------------------------------
<br>&gt; 
<br>&gt; Message: 5
<br>&gt; Date: Thu, 23 Dec 2010 09:07:35 -0600
<br>&gt; From: Chris &lt;<a href="mailto:jesdisciple@gmail.com">jesdisciple@gmail.com</a>&gt;
<br>&gt; Subject: Re: [rabbitmq-discuss] Installing RabbitMQ STOMP for PyGoWave
<br>&gt; To: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<br>&gt; Message-ID:
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &lt;<a href="mailto:AANLkTimsfciPxxXn8CQjhAJqfqKisMm0cEP7c4Oh80PU@mail.gmail.com">AANLkTimsfciPxxXn8CQjhAJqfqKisMm0cEP7c4Oh80PU@mail.gmail.com</a>&gt;
<br>&gt; Content-Type: text/plain; charset=&quot;iso-8859-1&quot;
<br>&gt; 
<br>&gt; Disregard my preious post; the plugins were only from a guide and I
<br>&gt; don't
<br>&gt; need the same ones.
<br>&gt; 
<br>&gt; In ALL things, strive for &gt;&lt;&gt;,
<br>&gt; Chris
<br>&gt; 
<br>&gt; 
<br>&gt; On Thu, Dec 23, 2010 at 12:16 AM, Chris &lt;<a href="mailto:jesdisciple@gmail.com">jesdisciple@gmail.com</a>&gt; wrote:
<br>&gt; 
<br>&gt; &gt; Also, I forgot to mention that I've upgraded to RabbitMQ 2.2.0.
<br>&gt; &gt; 
<br>&gt; -------------- next part --------------
<br>&gt; An HTML attachment was scrubbed...
<br>&gt; URL:
<br>&gt; &lt;<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101223/90180af6/attachment-0001.htm&gt;">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101223/90180af6/attachment-0001.htm&gt;</a>;
<br>&gt; 
<br>&gt; ------------------------------
<br>&gt; 
<br>&gt; Message: 6
<br>&gt; Date: Thu, 23 Dec 2010 17:59:15 &#43;0200
<br>&gt; From: yoav glazner &lt;<a href="mailto:yoavglazner@gmail.com">yoavglazner@gmail.com</a>&gt;
<br>&gt; Subject: Re: [rabbitmq-discuss] RabbitMQ for Master worker with
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  monitoring?
<br>&gt; To: rabbitmq-discuss &lt;<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>&gt;
<br>&gt; Message-ID:
<br>&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &lt;<a href="mailto:AANLkTikMzXgntxT7&#43;YHqm3rQ9oUGMc5SgvwZFvpS1pbS@mail.gmail.com">AANLkTikMzXgntxT7&#43;YHqm3rQ9oUGMc5SgvwZFvpS1pbS@mail.gmail.com</a>&gt;
<br>&gt; Content-Type: text/plain; charset=&quot;iso-8859-1&quot;
<br>&gt; 
<br>&gt; On Thu, Dec 23, 2010 at 3:35 PM, Emile Joubert &lt;<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>&gt;
<br>&gt; wrote:
<br>&gt; 
<br>&gt; &gt; Hi Yoav
<br>&gt; &gt; 
<br>&gt; &gt; 
<br>&gt; &gt; On 23/12/10 13:25, yoav glazner wrote:
<br>&gt; &gt; 
<br>&gt; &gt; &gt; 
<br>&gt; &gt; &gt; But then I'll lose messages when a worker die, no?
<br>&gt; &gt; &gt; 
<br>&gt; &gt; 
<br>&gt; &gt; Acknowledging messages only after successful processing will prevent
<br>&gt; them
<br>&gt; &gt; from being lost in case the consumer dies. If a consumer dies
<br>&gt; unacknowledged
<br>&gt; &gt; messages will be requeued.
<br>&gt; &gt; 
<br>&gt; &gt; Regards
<br>&gt; 
<br>&gt; 
<br>&gt; Thanks a lot for the input, I guess I'll have to dive in it now.
<br>&gt; -------------- next part --------------
<br>&gt; An HTML attachment was scrubbed...
<br>&gt; URL:
<br>&gt; &lt;<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101223/32dd9681/attachment.htm&gt;">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101223/32dd9681/attachment.htm&gt;</a>;
<br>&gt; 
<br>&gt; ------------------------------
<br>&gt; 
<br>&gt; _______________________________________________
<br>&gt; rabbitmq-discuss mailing list
<br>&gt; <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<br>&gt; <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a>
<br>&gt; 
<br>&gt; 
<br>&gt; End of rabbitmq-discuss Digest, Vol 43, Issue 64
<br>&gt; ************************************************
<br>&gt; 
<br><br></p>
</body>
</html>