Hi,
I recommend reading
http://qpid.apache.org/books/0.10/Programming-In-Apache-Qpid/html-single/Programming-In-Apache-Qpid.html#section-addresses.
Basically, a consumer subscribes itself to a queue so you should use queue name
in the address string (optionally followed by semicolon and queue attributes
like "queue_name; { create:always }"). While a producer produces messages (with
some routing key) via an exchange. So for producers you should specify their
address in form "<exchange_name>/<routing_key>", again optionally extended by
semicolon and node properties.
To make the basic flow complete, don't forget to create appropriate bindings to
let exchanges route messages into relevant queues.
Kind regards,
Pavel Moravec
----- Original Message -----
> From: "Senthil Kumar, Sinduja (GE Healthcare)" <sinduja.senthilku...@ge.com>
> To: users@qpid.apache.org
> Cc: pmora...@redhat.com
> Sent: Friday, February 3, 2012 1:01:26 PM
> Subject: RE: QUERY ON LOG FILES
>
> Hi,
> Thanks, I found out that.
> But actually Im to trying to implement the following scenario
> :Receiving Messages from Multiple Sources
>
> Server.cpp
> My address1 :
> Receiver receiver1 =
> session.createReceiver("service_queue/usa.news;{create:always}");
> My address2:
> Receiver receiver2 =
> session.createReceiver("service_queue/europe.news;{create:always}");
>
> Client1.cpp
> Sender sender = session.createSender("service_queue/europe.*");
> Client2.cpp
> Sender sender = session.createSender("service_queue/usa.*");
>
> Is this the way of setting two different addresses? Please help.
> Kindly tell me how to set two different addresses in this particular
> scenario.
>
> Regards,
> Sinduja.R
>
> -----Original Message-----
> From: Pavel Moravec [mailto:pmora...@redhat.com]
> Sent: Friday, February 03, 2012 5:27 PM
> To: users@qpid.apache.org
> Subject: Re: QUERY ON LOG FILES
>
> Hi Sinduja,
> you mean something like:
>
> qpid-config queues
> qpid-stat -q
>
> ?
>
> Kind regards,
> Pavel
>
> ----- Original Message -----
> > From: "Senthil Kumar, Sinduja (GE Healthcare)"
> > <sinduja.senthilku...@ge.com>
> > To: users@qpid.apache.org
> > Cc: pmora...@redhat.com
> > Sent: Friday, February 3, 2012 6:35:50 AM
> > Subject: RE: QUERY ON LOG FILES
> >
> > Hi,
> >
> > Can anyone tell me how to get the information about the list of
> > queues
> > available with a particular broker?
> >
> > Regards,
> > Sinduja.R
> >
> > -----Original Message-----
> > From: Pavel Moravec [mailto:pmora...@redhat.com]
> > Sent: Thursday, February 02, 2012 6:09 PM
> > To: users@qpid.apache.org
> > Subject: Re: QUERY ON LOG FILES
> >
> > Hi Sinduja,
> > see my response inline.
> >
> > Kind regards,
> > Pavel
> >
> > ----- Original Message -----
> > > From: "Senthil Kumar, Sinduja (GE Healthcare)"
> > > <sinduja.senthilku...@ge.com>
> > > To: users@qpid.apache.org
> > > Sent: Thursday, February 2, 2012 10:56:53 AM
> > > Subject: QUERY ON LOG FILES
> > >
> > > Hi,
> > >
> > >
> > >
> > > Can someone explain about the contents of the following three
> > > files
> > > created by the QPID broker.
> > >
> > >
> > >
> > > 1. .mbrokerdata
> > The file relevant to data directory contains three strings:
> > uuid bootSequence nextRemoteBank
> > where uuid is unique ID (as returned by uuid_generate) for the
> > broker
> > storage module that is using this data directory, bootSequence is
> > number of (re)starts of the broker and nextRemoteBank seems to be
> > 10
> > everytime (don't know its purpose, somehow relevant with storage
> > module)
> >
> > >
> > > 2. Lock
> > en empty file locked by the currently running qpid broker to
> > prevent
> > another qpid in using this data-dir in parallel
> >
> > >
> > > 3. systemId.
> > UUID (as returned by uuid_generate) of the broker.
> >
> >
> > >
> > >
> > >
> > > Regards,
> > >
> > > Sinduja.R
> > >
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:users-subscr...@qpid.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:users-subscr...@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
