[rabbitmq-discuss] Issue with .Net client Subscription

Paul Jones pauljones23 at gmail.com
Thu Sep 17 20:41:38 BST 2009

Hi Deepak,

Did you create a topic exchange? Wildcard routing keys in the form you're
using require a topic exchange.


On Thu, Sep 17, 2009 at 8:36 PM, <Deepak.Kumar1 at rbs.com> wrote:

> Hello
> Has anyone faced issues not getting messages when using catch-all
> subscription using the .Net Client library ?
> The publishing code is below -
> IConnection conn1 = new ConnectionFactory().CreateConnection(
> "localhost:5672");
> chSendUpdate = conn1.CreateModel();
> ...
> chSendUpdate.BasicPublish(string.Empty, "STOCK.PRICES." + CUSIP, null,
> Encoding.UTF8.GetBytes(bodyText));
> The subscription code is
> using (IConnection conn = new
> ConnectionFactory().CreateConnection("localhost:5672")){
>    using (IModel ch = conn.CreateModel())    {
>         Subscription sub = new Subscription(ch, "STOCK.PRICES.#");
>         foreach (BasicDeliverEventArgs e in sub)         {
>             Console.WriteLine("Topic({0}):{1}", e.RoutingKey,
> ASCIIEncoding.ASCII.GetString(e.Body));
>             sub.Ack(e);
>         }
>     }
>   }
> }
> If the subscription RoutingKey is changed to specific like
> "STOCK.PRICES.MSFT" etc. then the messages are received fine so i'm guessing
> there's some flag/option that needs to bet setup or enabled
> I've also tried the sample code in the .net user guide using
> QueueingBasicConsumer
> but no success there either
> Any ideas on what could be wrong ?
> *****Please note that my email address may have changed. For all
> future correspondence, please use this address*****
> ********************************************************************This
> message (including any attachments) is confidential and/or
> privileged. It is to be used by the intended recipients only. If
> you have received it by mistake please notify the sender by return
> e-mail and delete this message from your system. Any unauthorized
> use or dissemination of this message in whole or in part is
> strictly prohibited. Please note that e-mails are inherently
> insecure and susceptible to change. The Royal Bank of Scotland
> Group, plc ("RBS") and its US subsidiaries, and affiliates and
> subsidiary undertakings, including but not limited to, RBS plc New
> York and Connecticut Branches, RBS Securities Inc., ABN AMRO Bank
> N.V. New York and Chicago Branches and, ABN AMRO Incorporated,
> Citizens Financial Group, Inc. and RBS Citizens, N.A., shall not be
> liable for the improper or incomplete transmission of the
> information contained in this communication or Attachment nor for
> any delay in its receipt or damage to your system. RBS does not
> guarantee that the integrity of this communication has been
> maintained nor that this communication is free of viruses,
> interceptions or interference. RBS and its subsidiaries and
> affiliates do not guarantee the accuracy of any email or
> attachment, that an email will be received or that RBS or its
> affiliates and subsidiaries will respond to an email.
> RBS makes no representations that any information contained in this
> message (including any attachments) are appropriate for use in all
> locations or that transactions, securities, products, instruments
> or services discussed herein are available or appropriate for sale
> or use in all jurisdictions, or by all investors or counterparties.
> Those who utilize this information do so on their own initiative
> and are responsible for compliance with applicable local laws or
> regulations.********************************************************************
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090917/d7192255/attachment.htm 

More information about the rabbitmq-discuss mailing list