Re: Removing a receiver.

Ted Ross wrote > On 10/17/2013 04:32 PM, Rajesh Khan wrote: >> From the manual it states that you could read from multiple receivers >> and >> you could do that: >> by adding a receiver to a session as such: >> >> Receiver receiver1 = session.createReceiver(address1); >> >> Then you could simply r

Re: Building C++ broker persistence?

Gordon Sim wrote > I'm guessing one of the dependencies is not installed or perhaps that > some assumptions in the cmake build are unintentionally platform specific. > > You should be able to get a better message if you force > BUILD_LEGACYSTORE on. > > -

Re: AMQP 1.0 with Qpid Messaging API on Windows

Gordon Sim wrote > On 09/10/2013 08:30 AM, HrochL wrote: >> Hi, >> I was try to compile qpidc with AMQP 1.0 support on windows with >> MSVC2010. >> When linking the module amqpc.dll I got a lot of error messages >> "unresolved >> external symbol" - errors.txt >>

Re: Qpid Messaging API and topics

Gordon Sim wrote > On 10/03/2013 12:00 PM, HrochL wrote: >> Hi, >> I would like to use the Qpid Messaging API to send messages into ActiveMQ >> from my C++ program. I have a little problem with sending messages into >> topics. Address is always regarded as the address of the queue. I read >> here

Re: Create a collection of topics

+1 yes, its just creating senders for the amq.topic . As Gordon Sim said, it's good to create one sender to amq.topic and set the subject to each message. Gordon Sim wrote > It's not actually 'creating' topics, it is just creating senders for the > amq.topic topic, each with a specific default

Re: proton messenger performance (was Re: QPID AMQP Performance test)

+1 Gordon Sim wrote > On 09/30/2013 05:57 PM, amitg90 wrote: >> Hi All, >> >> i am new to QPID, after downloading the software from website, i used the >> sample example code (recv.c and send.c) and modified on send side to >> continuouly send 64 bytes packets from machine A and on recevie side on

Re: QPID AMQP Performance test

Gordon Sim wrote > On 10/01/2013 06:47 AM, NimbusParc wrote: >> Which version of QPID you are using while testing ? >> In the recent version of QPID-0.24, the --tcp-nodelay became Yes by >> default. >> If you are using previous versions, you need to pass this a

Re: QPID AMQP Performance test

Which version of QPID you are using while testing ? In the recent version of QPID-0.24, the --tcp-nodelay became Yes by default. If you are using previous versions, you need to pass this argument to get better performance. amitg90 wrote > Hi All, > > i am new to QPID, after downloading the sof

Re: New Fedora package: python-qpid_messaging

+1 Darryl L. Pierce wrote > The Swigged bindings have been packaged and are now available on Fedora > Linux as python-qpid_messaging. I've built for Fedora 18, 19 and 20 as > well as Rawhide. > > -- > Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > Delivering value year after year. > R

Re: survey: c++ broker and queue depth statistics

I would vote for (c) option. Gordon Sim wrote > The c++ broker reports a queue depth in terms of total bytes, as well as > the number of messages. > > For 0-10 the bytes statistic is calculated by aggregating only the > content size (i.e. the size of the body segment). For 1.0 it is the > wh

Re: Adding a new Qpid component: python_swig

+1 Ted Ross wrote > Darryl, > > I added "Python Client (Wrapped)" to the component list. > > -Ted > > On 09/27/2013 09:09 AM, Darryl L. Pierce wrote: >> Now that the Swigged Python library is out in the wild, at least in >> Fedora, can we add a new component for reporting features and bugs to >

RE: Possibility of a new release soon?

+1 Steve Huston wrote > Hi Graham, > >> I have just discovered I am affected by >> https://issues.apache.org/jira/browse/QPID-5113# which is marked as >> fixed, >> is there a plan for a release any time soon for qpid? > > Qpid releases are generally about 3 months apart, so it'll probably be > D

Re: survey: c++ broker and queue depth statistics

+1 Ted Ross wrote > I agree with Pavel and Jakub. Tying the "bytes" depth as closely as > possible to actual memory consumption is probably a good thing. We > could even consider counting the message overhead (the memory used that > is not part of the actual message). > > -Ted > > On 09/27/

Re: what is the difference between Exchange Route and Dynamic Exchange Route ?

kevency_poche wrote > i am playing with the broker federation. +1 Broker Federation is pretty interesting one. Keep playing, you will definitely enjoy the play. -- View this message in context: http://qpid.2158936.n2.nabble.com/what-is-the-difference-between-Exchange-Route-an

Re: what is the difference between Exchange Route and Dynamic Exchange Route ?

This tells kevency_poche wrote > I am not getting the exact difference between the Exchange Route and > Dynamic Exchange Route. > > In Exchange route we are giving the Routing key, but in dynamic exchange > routing we not even giving key also. > > What is the internal behavior of these two.

Re: Qpid-0.22 Static archive(.a) file does not exist ?

darkrwe wrote > But is it neccessary for compiling and linking -so files ? > i had known .a file is enough ? Archive libraries (.a) are statically linked i.e when you compile your program with -c option in gcc. So, if there's any change in library, you need to compile and build your code again.

Re: Qpid-0.22 Static archive(.a) file does not exist ?

Are you executing your programs in command line ?? if yes, how you are linking your library while executing, just post here. If you are using Eclipse, just check that you are including the library path correct or not ? darkrwe wrote > hi, > > I already add these classes to archive file. (as you

Re: Qpid hanging in qpid::messaging::createSession()?

+1 Gordon Sim wrote > On 06/21/2013 01:32 PM, Christian Fromme wrote: >> Hi, >> >> playing around with Qpid this got my attention: >> >> When the qpidd vanishes during a client calling this: >> >> Connection connection(url, connection_options); > > You need a connection.open() here. > >

Re: Qpid-0.22 Static archive(.a) file does not exist ?

darkrwe wrote > Hello, > > Thank you for your assistance. After I make the qpid-0.22, I find .o > files under .libs folders in src. > > But Although i add the all object files to the .a file when i compile the > project it gives undefined reference errors. > especially these errors are about: Ex

Re: Any way for topics to be deleted when the creator shuts down

+1 Gordon Sim wrote > On 09/10/2013 12:25 AM, Rajesh Khan wrote: >> Is there anyway for qpid to know that the sender has disconnected even if >> the sender does not elegantly disconnect by code ? > > The broker certainly knows that the sender has disconnected. To tie the > life of the node to th

Re: Qpid-0.22 Static archive(.a) file does not exist ?

darkrwe wrote > Unfortunately I could not see any ".a" file in build/src directory. There > are only shared object files. > > > how can i generate this .archive file for qpid ? or how can i find it ? > > As i know there is no way to generate this .a file from .so file. Because > .so file is lin

Re: Introducing Qpid Dispatch Router

Ted Ross wrote > I think you are somehow linking against an old proton library. Yes, i just removed the proton-0.4 and re-installed proton-0.5. Now qpid-dispatch built without any errors. Ted Ross wrote > On 09/18/2013 12:54 AM, NimbusParc wrote: >> yes, libqpid-proton.so.2.0.0

Re: Introducing Qpid Dispatch Router

yes, libqpid-proton.so.2.0.0 Ted Ross wrote > pn_connector_name was introduced in Proton 0.5. What version of the .so > file do you have installed? Is it libqpid-proton.so.2? > > -Ted > > On 09/17/2013 05:58 AM, NimbusParc wrote: >> Yes, i installed the latest pr

Re: Introducing Qpid Dispatch Router

ce to `pn_connector_name' collect2: ld returned 1 exit status make[2]: *** [libqpid-dispatch.so.0.1] Error 1 make[1]: *** [CMakeFiles/qpid-dispatch.dir/all] Error 2 make: *** [all] Error 2 Gordon Sim wrote > On 09/17/2013 07:59 AM, NimbusParc wrote: >> Error while doing make ..

Re: Introducing Qpid Dispatch Router

Error while doing make .. dispatch/src/server.c: In function ‘thread_process_listeners’: dispatch/src/server.c:103: error: implicit declaration of function ‘pn_connector_name’ make[2]: *** [CMakeFiles/qpid-dispatch.dir/src/server.c.o] Error 1 make[1]: *** [CMakeFiles/qpid-dispatch.dir/all] Error 2

Re: Dynamic Route and Duplicate Detection

+1 Ted Ross wrote > The qpid broker already does loop-suppression to prevent messages from > taking the same path more than once. The reason you get two messages is > because you have created a topology with redundant paths in it (i.e. > there are two distinct paths from each sender to each re

Re: executing qpid- c++ programs with g++ compiler

Here, The problem with the linking. You can use the following to execute the individual programs after installing the broker. Let us assume that you installed the broker with "cmake" in a separate directory * build/ *. you need to export the * LD_LIBRARY_PATH=/path/to/.so files/ * environmental

Re: qpid-config slow

Upgrade your qpid-tools.( Download from Official Website .) Also specify the broker while using the qpid-tools. if you specify the * -a * option it will take less than a second. Otherwise, it will take time and will be slo

Re: question about compiling qpidc-0.22

+1 Gordon Sim wrote > On 08/09/2013 11:44 PM, Ask Stack wrote: >> I like to have AMQP 1.0. Can you point me to a guild on how to do it ? >> thanks > > Install the proton protocol engine > (http://qpid.apache.org/components/protocol-engine/index.html), then > re-run cmake. > > (Note: If you ins

Re: C++ qpid::messaging::MessagingException::detail

+1 Gordon Sim wrote > On 08/20/2013 02:27 PM, Andrew Stitcher wrote: >> Gordon >> >> The (public) detail member of qpid::messaging::MessagingException struct >> doesn't seem to be used anywhere. >> >> * Is it in fact used somewhere I didn't notice? >> * I'm minded to remove it going forward, even

Re: How to test Qpid c++ broker ?

+1 Gordon Sim wrote > On 08/23/2013 02:08 PM, kevency_poche wrote: >> thank you very much Gordon. >> >>> For AMQP 0-10 you can set the content-type to 'text/plain' to indicate >>> that it is textual data, and of course you could set that to some other >>> mime-type to indicate some other binary fo

Re: fyi: qpidc and proton 0.5

+1 Gordon Sim wrote > There is a new release of proton to be posted shortly[1]. It has a > slight change to the protocol engine API, requiring an update of the > qpidc code that depends on it, so I'm going to make this change on > trunk. This will mean that the 1.0 support on trunk (and in the

Re: [python]ImportError: cannot import name ssl

Up to what i know, This is because of missing the package "python-qpid". This means that you need to install the "python-qpid". If you have "epel" repository in your "yum.repos.d/", You can directly install the package by searching like this. # yum search python-qpid In search r

Re: Help:qpid-python client doesn't work for qpid-0.22

Even though you installed the command line tools properly, sometimes you will get this error. This means that you need to install the "python-qpid". If you have "epel" repository in your "yum.repos.d/", You can directly install the package by searching like this. # yum search pytho

Re: Flow-to-disk functionality and its replacement in 0.24

+1 Gordon Sim wrote > On 09/02/2013 04:37 PM, Jakub Scholz wrote: >> Hi, >> >> I wanted to play with the new paged queues feature in 0.24RC3. I believe >> in >> the past it was planned that the old flow-to-disk functionality should be >> removed in 0.24 and the new paged queues should be introduce

Re: Dynamic routing between disconnected exchanges

+1 Ted Ross wrote > Ok, that's good. Can you try one more thing? > > Change the sequence of your setup: > > 1) Create exchanges > 2) Create dynamic routes > 3) Create queues and bindings > > I'm wondering if there's a bug in the code. > > -Ted -- View this message in context: http://qp

Re: Dynamic routing between disconnected exchanges

] => > 050aed7f-31c5-4018-ab99-f248b1789573:0.0 > Exchange 'qpid.management' (topic) > > > I really feel like I must be doing something wrong… > > Is there something that I can do to further debug the dynamic route > exchange? Or perhaps I could try manua

Re: [c++] give application more direct control over reconnect & replay

+1 Gordon Sim wrote > On 08/29/2013 04:11 PM, Gordon Sim wrote: >> On 08/29/2013 03:00 PM, Jakub Scholz wrote: >>> Right now, it seems that the reconnect(...) method always requires the >>> URL >>> of the broker to reconnect to. Maybe it would be useful to also add a >>> reconnect() method without

Re: Increasing number of messages normal?

+1 Ted Ross wrote > On 09/12/2013 05:44 AM, Christian Fromme wrote: >> Hi Gordon, >> >> thanks again for your quick reply. >> >> On Thu, Sep 12, 2013 at 11:25 AM, Gordon Sim < > gsim@ > > wrote: >> >>> I think the drops are caused by management events. The broker will >>> generate >>> events an

Re: [ANNOUNCE] Apache Qpid 0.24 released

+1 >The Apache Qpid community is pleased to announce the immediate >availability of Apache Qpid 0.24. >Apache Qpid (http://qpid.apache.org) is a cross-platform enterprise >messaging solution which implements the Advanced Message Queuing >Protocol (AMQP, http://www.amqp.org). It provides brok

Re: Removing the bindings from qpid-cpp source tarball...

Yes Darryl L. Pierce wrote > On Wed, Sep 11, 2013 at 10:02:24AM -0400, Darryl L. Pierce wrote: >> Gordon was installing the qpid-cpp 0.24 sources [1], which failed due to >> the LICENSE file for the Perl bindings not being present. After filling >> out a JIRA for this [2] and a comment from Gordo

Re: Increasing number of messages normal?

--Ted Ross wrote- If you run qpid-tool, it will subscribe to the updates. The qpid-printevents utility will subscribe to (and display) the events. +1 -- View this message in context: http://qpid.2158936.n2.nabble.com/Increasing-number-of-messages-normal-tp7598083p7

Re: Dynamic routing between disconnected exchanges

-bacon wrote- > Outout of qpid-stat -e on A after trying to send a message to b and then c > >Exchanges > exchangetype dur bind msgIn msgOut msgDrop byteIn > byteOut byteDrop > > >==

Re: Create a collection of topics

-Gordon Sim wrote- >[Both the c++ and java brokers are still heavily based on the old pre >-1.0 AMQP model of queues, exchanges and bindings which didn't have an >explicit concept of 'topic'. The common usage though is to have an >exchange for a topic, with the type c

Re: [ANNOUNCE] Apache Qpid 0.24 released

+1 >The Apache Qpid community is pleased to announce the immediate >availability of Apache Qpid 0.24. >Apache Qpid (http://qpid.apache.org) is a cross-platform enterprise >messaging solution which implements the Advanced Message Queuing >Protocol (AMQP, http://www.amqp.org). It provides brok

Re: [VOTE] Release Qpid 0.24

Original Message > http://people.apache.org/~jross/qpid-0.24-rc4/ > If you favor releasing RC4 as Qpid 0.24 GA, vote +1. +1 -- View this message in context: http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-0-24-tp7597516p7597696.html Sent from the

Re: Any one have compiled qpid on Pidora?

sundawei Wrote :--- > It take so long > to compile from the source and at last ended with error. What is that error you got while compiling ? -- View this message in context: http://qpid.2158936.n2.nabble.com/Any-one-have-compiled-qpid-on-Pidora-tp7594460p7597238.html Sent from t

Re: tcp-nodelay on broker

-Andrew that's good catch. Thank you -- View this message in context: http://qpid.2158936.n2.nabble.com/tcp-nodelay-on-broker-tp7595208p7597237.html Sent from the Apache Qpid users mailing list archive at Nabble.com. - To uns

Re: tcp-nodelay on broker

yes, --tcp-nodelay became default in qpidc-0.24.But, still it is showing as an optional one in *qpidd -h * menu. Need to edit that one. -- View this message in context: http://qpid.2158936.n2.nabble.com/tcp-nodelay-on-broker-tp7595208p7597117.html Sent from the Apache Qpid users mail

Re: Help:qpid-python client doesn't work for qpid-0.22

These Exceptions tells the Installation was not successful. To install properly .. 1. first download from official website http://qpid.apache.org/download.html .2. Untar it and enter into qpid-tools directory.3. Run * ./setup.py build * and