Re: Removing a receiver.

2013-10-20 Thread NimbusParc 
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 read it:
>> Message message = session.nextReceiver().fetch();
>>
>> Now my question is how do I remove a receiver once I do not want to
>> receive
>> from it ?
>>
> 
> You can call  receiver1.close().
> 
> -Ted
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache

+1



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Removing-a-receiver-tp7599646p7599689.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Building C++ broker persistence?

2013-10-07 Thread NimbusParc 
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.
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache

+1



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Building-C-broker-persistence-tp7599056p7599107.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: AMQP 1.0 with Qpid Messaging API on Windows

2013-10-04 Thread NimbusParc 
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
>> ;  . In
>> linker
>> settings i have depenedencies on qpidcommon.lib, qpidclient.lib,
>> qpidmessaging.lib, qpidtypes.lib and qpid-proton.lib.
>> Can someone tell me what is the problem?
> 
> There were several symbols that weren't being exported. This was my 
> fault, I do apologise. The good news is that thanks to Chuck, it is now 
> fixed: https://issues.apache.org/jira/browse/QPID-5102
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache

+1



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/AMQP-1-0-with-Qpid-Messaging-API-on-Windows-tp7598035p7598993.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Qpid Messaging API and topics

2013-10-03 Thread NimbusParc 
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
>> ;   that it is necessary to
>> use prefix
>> "topic://". But when I do it, the message is delivered to the queue named
>> "topic:" and rest of the address is used as subject of the message.
>> What am I doing wrong?
> 
> Short answer: you need to put quotes around the url. E.g.
> 
>session.createReceiver("'topic://my-topic-name'");
> 
> (note the single quotes inside the string literal).
> 
> The reason for this is that the qpid messaging API assumes addresses in 
> the form 
> 
> /
> 
> , so without quoting it takes the portion 
> up to the first '/' as the node name, and everything thereafter as the 
> subject.
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache

+1



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-Messaging-API-and-topics-tp7598962p7598966.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Create a collection of topics

2013-10-03 Thread NimbusParc 
+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 subject.
> 
> So you could just create one sender to amq.topic, and then set the 
> subject of each message you send out.
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Create-a-collection-of-topics-tp7597987p7598961.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-10-01 Thread NimbusParc 
+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
>> machine B grabbing the packet and checking how much packets i received
>> per
>> sec and i am not able to see more than 18000 packets per sec (throughput
>> 10Mbps).
>>
>> being a 1Gbps link between two machines i was hoping for more throughput
>> coming out of it..
>>
>> i ran standard TCP performance test and it get close to 800Mbps
>> throughput.
>>
>> can someone please suggest if there is something obvious that i am
>> missing
>> or there exist some performance script which help me understand what is
>> causing low throughput..
> 
> There are two test programs that report throughput and latency for 
> different scenarios. The executables are built under 
> 
> /tests/tools/apps/c/ and are called msgr-send and msgr-recv.
> 
> E.g. for a one-way test, start
> 
> /tests/tools/apps/c/msgr-recv -c 100
> 
> then in another console:
> 
> /tests/tools/apps/c/msgr-send -c 100 -b 64
> 
> The message size is controlled with the -b option. You can vary the 
> batch size for send with -p option. You can also run a two way test, 
> where the receiver echoes the messages back using the -R option to each. 
> By default messages are sent presettled, you can change that by setting 
> a non zero outgoing window with the -w option.
> 
> On my laptop, over loopback, I get about 50k 64 byte msgs/sec using the 
> default batch size of 1024. With a batch size of 1, that drops to about 
> 25k msgs/sec.
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/QPID-AMQP-Performance-test-tp7598833p7598856.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID AMQP Performance test

2013-10-01 Thread NimbusParc 
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 argument to
>> get
>> better performance.
> 
> Just for clarification, I suspect (given the executable names) that the 
> question was referring to proton messenger which is on its own release 
> cycle (0.5 being the latest) and where there is no tcp-nodelay option.

Oh.. When answering to this question, i am just doing the same performance
test for my C++ broker.
At that time by seeing this question, i  know this is about proton messenger
but i don't know why i 
answered for the C++ broker. It was totally due to my deep involvement  in
testing the C++ broker.
 Excuse me and What you answered above is very good with clear explanation. 

Gordon Sim wrote
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/QPID-AMQP-Performance-test-tp7598833p7598855.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID AMQP Performance test

2013-09-30 Thread NimbusParc 
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 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
> machine B grabbing the packet and checking how much packets i received per
> sec and i am not able to see more than 18000 packets per sec (throughput
> 10Mbps).
> 
> being a 1Gbps link between two machines i was hoping for more throughput
> coming out of it.. 
> 
> i ran standard TCP performance test and it get close to 800Mbps
> throughput.
> 
> can someone please suggest if there is something obvious that i am missing
> or there exist some performance script which help me understand what is
> causing low throughput..
> 
> i can provide more details if that helps..
> 
> thanks
> amit





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/QPID-AMQP-Performance-test-tp7598833p7598848.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: New Fedora package: python-qpid_messaging

2013-09-30 Thread NimbusParc 
+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.
> Red Hat ranks #1 in value among software vendors.
> http://www.redhat.com/promo/vendor/
> 
> 
> 
> attachment0 (205 bytes)
> ;





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/New-Fedora-package-python-qpid-messaging-tp7598585p7598797.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-30 Thread NimbusParc 
 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 
> whole message including properties etc (i.e. the payload of the transfer 
> 'performative').
> 
> So the size will be different depending on the protocol used in sending 
> it and this difference can be quite marked. E.g. in an extreme case 
> where there are many headers but no content, the bytes reported if sent 
> over 0-10 would be 0 whereas if sent over 1.0 could easily be several 
> hundred bytes.
> 
> The question is what to do about this. The options are (a) accept that 
> they are inconsistent between versions, (b) modify the 1.0 path to only 
> record the application-data or (c) modify the 0-10 path to include the 
> size of the header segment.
> 
> While (c) seems to me to be logical the most 'correct', it would be a 
> difference in behaviour. It would mean for example that any queue limits 
> would be hit earlier. One could argue that would be an improvement, but 
> it may cause issues for systems when upgrading.
> 
> The purpose of this mail is to solicit some feedback from users as to 
> which of these options (or indeed other options that have not occurred 
> to me) would be preferable.
> 
> --Gordon.
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/survey-c-broker-and-queue-depth-statistics-tp7598657p7598792.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Adding a new Qpid component: python_swig

2013-09-30 Thread NimbusParc 
+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
>> differentiate them from the pure Python bindings?
>>
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Adding-a-new-Qpid-component-python-swig-tp7598676p7598794.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

RE: Possibility of a new release soon?

2013-09-30 Thread NimbusParc 
+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
> December or so before 0.26 is released with that fix.
> 
> 
> -Steve
> 
> --
> Steve Huston, Riverace Corporation
> Total Lifecycle Support for Your Networked Applications
> http://www.riverace.com 
> 
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Possibility-of-a-new-release-soon-tp7598724p7598793.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-30 Thread NimbusParc 
+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/2013 08:01 AM, Pavel Moravec wrote:
>> I would vote for (c) option.
>>
>> Negs:
>> - "backward incompatible" change
>>
>> Pros:
>> - the incompatibility requires just a change in one type of number during
>> one upgrade
>> - calculation of message size should be unified - assume a queue
>> enqueuing messages from 1.0 and 0-10 client
>> - limiting queue in "size" units is IMHO useful to limit memory
>> consumption of the queue - where counting message headers in the limit
>> makes more sense
>>
>> Kind regards,
>> Pavel
>>
>>
>>
>> - Original Message -
>>> From: "Gordon Sim" <

> gsim@

> >
>>> To: 

> users@.apache

>>> Sent: Friday, September 27, 2013 1:04:17 PM
>>> Subject: Re: survey: c++ broker and queue depth statistics
>>>
>>> On 09/27/2013 11:47 AM, 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
 whole message including properties etc (i.e. the payload of the
 transfer
 'performative').

 So the size will be different depending on the protocol used in sending
 it and this difference can be quite marked. E.g. in an extreme case
 where there are many headers but no content, the bytes reported if sent
 over 0-10 would be 0 whereas if sent over 1.0 could easily be several
 hundred bytes.

 The question is what to do about this. The options are (a) accept that
 they are inconsistent between versions, (b) modify the 1.0 path to only
 record the application-data or (c) modify the 0-10 path to include the
 size of the header segment.
>>> I should point out that neither (b) or (c) give identical sizes for the
>>> same application data due to minor differences in the two type systems.
>>> However the difference would be fairly small and relatively fixed
>>> whereas for (a) it can vary hugely depending on the exact message.
>>>
>>> An option (d) would be to try and come up with a scheme where the size
>>> would be always identical. I'm not hugely keen on this as it would add
>>> overhead (e.g. calculating the size of a set of 0-10 headers if encoded
>>> in the 1.0 type scheme).
>>>
 While (c) seems to me to be logical the most 'correct', it would be a
 difference in behaviour. It would mean for example that any queue
 limits
 would be hit earlier. One could argue that would be an improvement, but
 it may cause issues for systems when upgrading.

 The purpose of this mail is to solicit some feedback from users as to
 which of these options (or indeed other options that have not occurred
 to me) would be preferable.

 --Gordon.

 -
 To unsubscribe, e-mail: 

> users-unsubscribe@.apache

 For additional commands, e-mail: 

> users-help@.apache


>>>
>>> -
>>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>>> For additional commands, e-mail: 

> users-help@.apache

>>>
>>>
>> -
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache

>>
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/survey-c-broker-and-queue-depth-statistics-tp7598657p7598791.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-23 Thread NimbusParc 
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-and-Dynamic-Exchange-Route-tp7598468p7598470.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-23 Thread NimbusParc 
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.  ??

   This means you are not clear about the Broker Federation. There are three
routes in the broker federation. 
They are 1. Queue Route.
  2. Exchange Route.
  3. Dynamic Exchange Route.

Now, i will talk only about the Internal behavior of the Exchange route and
Dynamic Route.

Exchange Route :


 Internally, creating an exchange route creates a private
queue (auto-delete, exclusive) on the source broker
to hold messages that are to be routed to the destination broker, binds this
private queue to the source broker exchange,
 and subscribes the destination broker to the queue.

Dynamic Exchange Route:
---

Internally, Dynamic exchange routes apply all the bindings
of a destination exchange to a source exchange,
 so that any message that would match one of these bindings is routed to the
destination exchange. If bindings are added
or removed from the destination exchange, these changes are reflected in the
dynamic exchange route -- when the
 destination broker creates a binding with a given binding key, this is
reflected in the route, and when the destination broker 
drops a binding with a binding key

Also, go through the documentation..  Federation Documentation

  





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/what-is-the-difference-between-Exchange-Route-and-Dynamic-Exchange-Route-tp7598468p7598469.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-22 Thread NimbusParc 
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.

The advantage of .so (shared object) over .a library is that they are linked
during the runtime
 i.e. after creation of your .o file -o option in gcc. So, if there's any
change in .so file, 
you don't need to recompile your main program.  But make sure that your main
program is linked to the 
new .so file with ln command.



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-0-22-Static-archive-a-file-does-not-exist-tp7598234p7598387.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-22 Thread NimbusParc 
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 said qpid new
> messaging api uses sys framing and etc classes)
> 
> But is it neccessary for compiling and linking -so files ? 
> i had known .a file is enough ?





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-0-22-Static-archive-a-file-does-not-exist-tp7598234p7598386.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-20 Thread NimbusParc 
+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.
> 
>>  Session session = connection.createSession();
>>  Sender sender = session.createSender(foo);
>>
>> I get this in the client:
>>
>> #0  0xe424 in __kernel_vsyscall ()
>> #1  0xb4c089d6 in nanosleep () from /lib/libc.so.6
>> #2  0xb4c3a8ac in usleep () from /lib/libc.so.6
>> #3  0xb5968e72 in qpid::sys::usleep(unsigned long long) () from
>> /opt/qpid/qpid-0.20-1dfs/lib/libqpidcommon.so.2
>> #4  0xb785c34f in
>> qpid::client::amqp0_10::ConnectionImpl::connect(qpid::sys::AbsTime
>> const&) () from /opt/qpid/qpid-0.20-1dfs/lib/libqpidmessaging.so.2
>> #5  0xb785c636 in qpid::client::amqp0_10::ConnectionImpl::open() ()
>> from /opt/qpid/qpid-0.20-1dfs/lib/libqpidmessaging.so.2
>> #6  0xb78589e4 in qpid::client::amqp0_10::ConnectionImpl::reopen() ()
>> from /opt/qpid/qpid-0.20-1dfs/lib/libqpidmessaging.so.2
>> #7  0xb7858fa9 in
>> qpid::client::amqp0_10::ConnectionImpl::newSession(bool, std::string
>> const&) () from /opt/qpid/qpid-0.20-1dfs/lib/libqpidmessaging.so.2
>> #8  0xb782866e in
>> qpid::messaging::Connection::createSession(std::string const&) () from
>> /opt/qpid/qpid-0.20-1dfs/lib/libqpidmessaging.so.2
>>
>> And it seems to never return. No exception. Nothing. Is this a known
>> issue? Can I tweak around the connection options to change this
>> (currently got: "{reconnect:true,heartbeat:5}")?
> 
> The stack trace shows it is trying to 'reconnect'. This may be because 
> the connection was not actually opened in the first place(?). In any 
> case this would happen if the connection was established and was then 
> lost. If the broker(s) specified never become available then the 
> reconnect will never succeed. You can limit the time or number of 
> retries with some combination of the following:
> 
> - reconnect_timeout: seconds (give up and report failure after specified 
> time)
> - reconnect_limit: n (give up and report failure after specified number 
> of attempts)
> - reconnect_interval_min: seconds (initial delay between failed 
> reconnection attempts)
> - reconnect_interval_max: seconds (maximum delay between failed 
> reconnection attempts)
> - reconnect_interval: shorthand for setting the same 
> reconnect_interval_min/max
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-hanging-in-qpid-messaging-createSession-tp7594408p7598313.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-20 Thread NimbusParc 
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: Exceptions, sys, client, and framing
> classes. (some methods cannot be find)
> i just collect all object files to a folder and execute ar rvs
> libqpid-0.22.a *.o command.

As for as i know..
you should add all the object files, (i.e,.)  Exceptions, sys, client, and
framing classes object files to your static library. 
Because, The classes you are using in your project calling those (
Exceptions, sys, client, and framing ) classes internally. 


darkrwe wrote
> then of course i added to "qpid-0.22" to my libraries and i set the
> library path.

Anyways you are adding your libraries to path. Also add the path of .so
files to library path.
Then you will not get any linking errors.


darkrwe wrote
> in my project i just use below classes:
> 
> "qpid/messaging/Address.h"
> "qpid/messaging/Connection.h"
> "qpid/messaging/Message.h"
> "qpid/messaging/Receiver.h"
> "qpid/messaging/Sender.h"
> "qpid/messaging/Session.h"
> 
> here are my errors.
> eclipse-cdt-errors
>   
> 
> is there any idea what is my wrong ? 
> Thank you very much again.





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-0-22-Static-archive-a-file-does-not-exist-tp7598234p7598311.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-19 Thread NimbusParc 
+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 that of the sender you require some way to express 
> that association.
> 
> In AMQP 0-10 the only way to do so is really to declare the queue as 
> exclusive and auto-delete, which isn't really what you want and wouldn't 
> work for exchanges (i.e. 'topic nodes') anyway.
> 
> In AMQP 1.0 a sender has a link to the node, and providing the node is 
> created when that link is established you can tie the life of the node 
> to the life of that link.
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Any-way-for-topics-to-be-deleted-when-the-creator-shuts-down-tp7598017p7598288.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-18 Thread NimbusParc 
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 linked? 
> 
> so i think i need to compile all qpid project but it is not a good way. 
> for example there are many class dependencies for qpid messaging libraries
> that I using.

As for as i know..
 If you build with cmake, you will find only .so files in your "build/src"
directory. 
But, if you want ".a" files, there is one way to get them. You can use *
make * to build.
 (I don't recommend this method, because make is already deprecated )

 If you build with make, then you will find one hidden directory ".libs/" in
your "src/" directory which contains .so and .la files. 
And if you goto the directories like "qpid/", "qmf/", etc,. you will find
".libs/", inside each directory with .o files, useful to create ".a"
library.
You can create your own .a library with the object files. 

If you don't know how to make ".a" library with ".o" files, go through this. 
http://www.delorie.com/djgpp/v2faq/faq8_22.html
  .

All the best.




darkrwe wrote
> 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 linked?
> 
> so i think i need to compile all qpid project but it is not a good way. 
> for example there are many class dependencies for qpid messaging libraries
> that I using.
> 
> I also found some tools (ermine , Statifier) But actually they just use
> executables. They dont convert .so to .a file or such as operation.
> 
> what do you suggest to me guys ?
> 
> My best Regards.
> Emin.





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-0-22-Static-archive-a-file-does-not-exist-tp7598234p7598287.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Introducing Qpid Dispatch Router

2013-09-18 Thread NimbusParc 
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
>>
>>
>> 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 proton libraries (0.5) and also cmake build
>>>> configuration to point proton .so files.
>>>> As shown below, In my CMakeCache.txt..
>>>>
>>>> //Path to a library.
>>>> proton_lib:FILEPATH=/usr/lib64/libqpid-proton.so
>>>>
>>>> After adding the path of .so files, which are in proton-c/  directory
>>>> to
>>>> *
>>>> LD_LIBRARY_PATH *. And then running make again.
>>>> I am getting this error while linking to the c shared library *
>>>> libqpid-dispatch.so *. Results given below..
>>>>
>>>> Scanning dependencies of target qpid-dispatch
>>>> [  3%] Building C object CMakeFiles/qpid-dispatch.dir/src/agent.c.o
>>>> [  6%] Building C object CMakeFiles/qpid-dispatch.dir/src/alloc.c.o
>>>> 
>>>> 
>>>> [ 63%] Building C object
>>>> CMakeFiles/qpid-dispatch.dir/src/work_queue.c.o
>>>> Linking C shared library libqpid-dispatch.so
>>>> CMakeFiles/qpid-dispatch.dir/src/server.c.o: In function
>>>> `thread_process_listeners':
>>>> server.c:(.text+0x285): undefined reference 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 ..
>>>>>>
>>>>>> 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
>>>>>> make: *** [all] Error 2
>>>>> Do you have the latest proton libraries (0.5) and is the cmake build
>>>>> configured to point at them?
>>>>>
>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail:
>>>>> users-unsubscribe@.apache
>>>>> For additional commands, e-mail:
>>>>> users-help@.apache
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598230.html
>>>> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>>>>
>>>> -
>>>> To unsubscribe, e-mail:
>>> users-unsubscribe@.apache
>>>> For additional commands, e-mail:
>>> users-help@.apache
>>>
>>> -
>>> To unsubscribe, e-mail:
>>> users-unsubscribe@.apache
>>> For additional commands, e-mail:
>>> users-help@.apache
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598248.html
>> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>>
>> -
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache

>>
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598286.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Introducing Qpid Dispatch Router

2013-09-17 Thread NimbusParc 
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 proton libraries (0.5) and also cmake build
>> configuration to point proton .so files.
>> As shown below, In my CMakeCache.txt..
>>
>> //Path to a library.
>> proton_lib:FILEPATH=/usr/lib64/libqpid-proton.so
>>
>> After adding the path of .so files, which are in proton-c/  directory to
>> *
>> LD_LIBRARY_PATH *. And then running make again.
>> I am getting this error while linking to the c shared library *
>> libqpid-dispatch.so *. Results given below..
>>
>> Scanning dependencies of target qpid-dispatch
>> [  3%] Building C object CMakeFiles/qpid-dispatch.dir/src/agent.c.o
>> [  6%] Building C object CMakeFiles/qpid-dispatch.dir/src/alloc.c.o
>> 
>> 
>> [ 63%] Building C object CMakeFiles/qpid-dispatch.dir/src/work_queue.c.o
>> Linking C shared library libqpid-dispatch.so
>> CMakeFiles/qpid-dispatch.dir/src/server.c.o: In function
>> `thread_process_listeners':
>> server.c:(.text+0x285): undefined reference 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 ..
>>>>
>>>> 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
>>>> make: *** [all] Error 2
>>> Do you have the latest proton libraries (0.5) and is the cmake build
>>> configured to point at them?
>>>
>>>
>>> -
>>> To unsubscribe, e-mail:
>>> users-unsubscribe@.apache
>>> For additional commands, e-mail:
>>> users-help@.apache
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598230.html
>> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>>
>> -
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache

>>
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598248.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Introducing Qpid Dispatch Router

2013-09-17 Thread NimbusParc 
Yes, i installed the latest proton libraries (0.5) and also cmake build
configuration to point proton .so files.
As shown below, In my CMakeCache.txt..

//Path to a library.
proton_lib:FILEPATH=/usr/lib64/libqpid-proton.so

After adding the path of .so files, which are in proton-c/  directory to *
LD_LIBRARY_PATH *. And then running make again.
I am getting this error while linking to the c shared library *
libqpid-dispatch.so *. Results given below..

Scanning dependencies of target qpid-dispatch
[  3%] Building C object CMakeFiles/qpid-dispatch.dir/src/agent.c.o
[  6%] Building C object CMakeFiles/qpid-dispatch.dir/src/alloc.c.o


[ 63%] Building C object CMakeFiles/qpid-dispatch.dir/src/work_queue.c.o
Linking C shared library libqpid-dispatch.so
CMakeFiles/qpid-dispatch.dir/src/server.c.o: In function
`thread_process_listeners':
server.c:(.text+0x285): undefined reference 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 ..
>>
>> 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
>> make: *** [all] Error 2
> 
> Do you have the latest proton libraries (0.5) and is the cmake build 
> configured to point at them?
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598230.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Introducing Qpid Dispatch Router

2013-09-17 Thread NimbusParc 
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
make: *** [all] Error 2



Ted Ross wrote
> I've been working on a sub-project within Apache Qpid called Qpid 
> Dispatch Router.  I'd like to invite use, participation, feedback, 
> criticism, etc.
> 
> There are a couple of basic introductory points to be made:
> 
>   * Dispatch Router is built on top of the Qpid Proton engine and driver
> APIs (The C implementations thereof).
>   * A router is not a broker.  The idea of a message router was born
> from the awkwardness of trying to build scaled-up messaging networks
> out of brokers.
>   * A network built from routers provides interconnect between brokers,
> between clients and brokers, or between clients and clients (i.e.
> point-to-point non-brokered).
>   * The message router brings together the two separate worlds of
> Messaging and Networking.  Such a confluence was made possible by
> the AMQP 1.0 protocol.  The vision is to provide a messaging
> interconnect that has all the advanced semantics of AMQP along with
> the scale, resiliency, and ease of deployment of an IP network.
> 
> The code is in early stages of development and has not been through any 
> kind of release.  It builds only in Posix-based environments (Linux, 
> etc.) and it only functions as a single stand-alone router at present 
> (inter-router links are not yet fully implemented).  The router can be 
> used with both the Proton Messenger API and the Qpid Messaging Client 
> APIs that support AMQP 1.0 (and, in theory, with any AMQP 1.0 endpoint).
> 
> The code can be found in the Subversion tree under "qpid/extras/dispatch".
> 
> http://svn.apache.org/repos/asf/qpid/trunk/qpid/extras/dispatch
> 
> There is a draft web page for it here:
> 
>  http://qpid.apache.org/components/dispatch-router/index.html
> 
> Qpid Dispatch Router will provide two basic mechanisms for message 
> routing.  *Message Routing* forwards individual messages to their 
> destination(s) based on the address in the message's "to" field. *Link 
> Routing* propagates link-attaches across the network to the peer 
> addressed in the link's "source" or "target" field.  This is similar to 
> creating a "virtual channel" across the network and allows the full 
> semantics (transactions, flow-control, etc.) to be provided end-to-end 
> (as though the participating endpoints were directly connected).  
> Currently, only Message Routing is implemented.
> 
> The following is a brief example of the router's use to illustrate how 
> it works:
> 
> [Refer to the README file for building instructions]
> [The router executable and Proton Messenger examples are assumed to be 
> in the execution path]
> 
> Run the following in separate terminal windows:
> 
> $ router/dispatch-router -c 
> 
> $ recv amqp://0.0.0.0:5672/my_address/1
> $ recv amqp://0.0.0.0:5672/my_address/1
> $ recv amqp://0.0.0.0:5672/my_address/another
> $ send -a amqp://0.0.0.0:5672/my_address/1 CONTENT
> $ send -a amqp://0.0.0.0:5672/my_address/another CONTENT
> 
> The first line starts the router process (assumed to be configured to 
> listen on port 5672).  The "recv" examples create connections to the 
> router and subscribe to two different address (two use the same 
> address).  The "send" examples create connections to the router and send 
> messages to their respective addresses.
> 
> If everything works, the first sent message will be received by the 
> first two receivers and the second sent message will be received only by 
> the third receiver.
> 
> Regards,
> 
> -Ted





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Introducing-Qpid-Dispatch-Router-tp7598222p7598228.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Dynamic Route and Duplicate Detection

2013-09-16 Thread NimbusParc 
+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 receiver).  Your 
> receiver will receive one copy of the message for each distinct path 
> through the topology.  If you expand your broker network with more 
> redundancy, you will potentially receive many more copies of each message.
> 
> The qpid clients do not prevent delivery of duplicate messages.  You can 
> layer such a capability on top of the clients if you wish.  The other 
> thing you can do is to break the loop in your topology (close one of the 
> federation links) to prevent duplication.
> 
> -Ted
> 
> On 06/27/2013 05:24 AM, 

> rajib.x.majumder@

>  wrote:
>>
>> Hi,
>>
>> I am using broker federation in qpid 0.20 C++ broker and have a 3 
>> broker topology as attached.
>>
>> I have configured bidirectional dynamic routes for "amq.direct" 
>> exchange for the 3 brokers as shown attached.
>>
>> When I publish a  message from qpid JMS to 1001 and receive it from 
>> qpid JMS on 10003, I get 2 messages, instead of 1.
>>
>> Can qpid do duplicate detection and delivery only 1 message ?
>>
>> Thanks
>>
>> Rajib
>>
>> ___
>>
>> This message is for information purposes only, it is not a 
>> recommendation, advice, offer or solicitation to buy or sell a product 
>> or service nor an official confirmation of any transaction. It is 
>> directed at persons who are professionals and is not intended for 
>> retail customer use. Intended for recipient only. This message is 
>> subject to the terms at: www.barclays.com/emaildisclaimer 
>> ;.
>>
>> For important disclosures, please see: 
>> www.barclays.com/salesandtradingdisclaimer 
>> ; regarding
>> market 
>> commentary from Barclays Sales and/or Trading, who are active market 
>> participants; and in respect of Barclays Research, including 
>> disclosures relating to specific issuers, please see 
>> http://publicresearch.barclays.com.
>>
>> ___
>>
>>
>>
>> -
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Dynamic-Route-and-Duplicate-Detection-tp7594629p7598227.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-16 Thread NimbusParc 
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 variable. Then..

$ g++ -o hello hello_world.cpp -I /path/to/include/directory/in/qpid -L
/path/to/.so files/in/build/src/folder -lqpidmessaging 

Also, link * -lqpidtypes * if needed.

This will execute your programs. 


RajendraNPTL wrote
> hello all 
> i am new to qpid. i am trying to execute the hello world program with g++
> compilor specifically (with out "make")
> but, i am getting some errors. any body have idea regarding this ??? ( i
> am using centos 6.3)
> 
> $ > g++ -o hello hello_world.cpp -I /home/qpid-0.18/cpp/include/
> /tmp/cczB9Ivi.o: In function `main':
> hello_world.cpp:(.text+0x169): undefined reference to
> `qpid::messaging::Connection::Connection(std::basic_string std::char_traits, std::allocator
> 
>  > const&, std::basic_string,
> std::allocator
> 
>  > const&)'
> hello_world.cpp:(.text+0x178): undefined reference to
> `qpid::messaging::Connection::open()'
> hello_world.cpp:(.text+0x1a1): undefined reference to
> `qpid::messaging::Connection::createSession(std::basic_string std::char_traits, std::allocator
> 
>  > const&)'
> hello_world.cpp:(.text+0x1e8): undefined reference to
> `qpid::messaging::Session::createReceiver(std::basic_string std::char_traits, std::allocator
> 
>  > const&)'
> hello_world.cpp:(.text+0x205): undefined reference to
> `qpid::messaging::Session::createSender(std::basic_string std::char_traits, std::allocator
> 
>  > const&)'
> hello_world.cpp:(.text+0x239): undefined reference to
> `qpid::messaging::Message::Message(std::basic_string std::char_traits, std::allocator
> 
>  > const&)'
> hello_world.cpp:(.text+0x254): undefined reference to
> `qpid::messaging::Sender::send(qpid::messaging::Message const&, bool)'
> hello_world.cpp:(.text+0x267): undefined reference to
> `qpid::messaging::Message::~Message()'
> hello_world.cpp:(.text+0x27b): undefined reference to
> `qpid::messaging::Message::~Message()'
> hello_world.cpp:(.text+0x2d6): undefined reference to
> `qpid::messaging::Duration::SECOND'
> hello_world.cpp:(.text+0x2db): undefined reference to
> `qpid::messaging::operator*(qpid::messaging::Duration const&, unsigned
> long)'
> hello_world.cpp:(.text+0x2f7): undefined reference to
> `qpid::messaging::Receiver::fetch(qpid::messaging::Duration)'
> hello_world.cpp:(.text+0x30d): undefined reference to
> `qpid::messaging::Message::getContent() const'
> hello_world.cpp:(.text+0x366): undefined reference to
> `qpid::messaging::Session::acknowledge(bool)'
> hello_world.cpp:(.text+0x375): undefined reference to
> `qpid::messaging::Connection::close()'
> hello_world.cpp:(.text+0x389): undefined reference to
> `qpid::messaging::Message::~Message()'
> hello_world.cpp:(.text+0x39f): undefined reference to
> `qpid::messaging::Message::~Message()'
> hello_world.cpp:(.text+0x3bb): undefined reference to
> `qpid::messaging::Sender::~Sender()'
> hello_world.cpp:(.text+0x3d2): undefined reference to
> `qpid::messaging::Sender::~Sender()'
> hello_world.cpp:(.text+0x3e8): undefined reference to
> `qpid::messaging::Receiver::~Receiver()'
> hello_world.cpp:(.text+0x3ff): undefined reference to
> `qpid::messaging::Receiver::~Receiver()'
> hello_world.cpp:(.text+0x415): undefined reference to
> `qpid::messaging::Session::~Session()'
> hello_world.cpp:(.text+0x42c): undefined reference to
> `qpid::messaging::Session::~Session()'
> hello_world.cpp:(.text+0x483): undefined reference to
> `qpid::messaging::Connection::close()'
> hello_world.cpp:(.text+0x4b5): undefined reference to
> `qpid::messaging::Connection::~Connection()'
> hello_world.cpp:(.text+0x4cc): undefined reference to
> `qpid::messaging::Connection::~Connection()'
> collect2: ld returned 1 exit status
> 
> thank you in advance





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/executing-qpid-c-programs-with-g-compiler-tp7590258p7598206.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: qpid-config slow

2013-09-16 Thread NimbusParc 
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 slow.

(i.e). To create a queue...* $ qpid-config add queue my_queue -a
[broker-address] *



RajendraNPTL wrote
> Ya.. it is too slow.. For me it is taking 7 sec nearly.. 

> 
> real  0m6.933s
> user  0m0.319s
> sys   0m0.028s





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/qpid-config-slow-tp6602945p7598205.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: question about compiling qpidc-0.22

2013-09-16 Thread NimbusParc 
+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 install proton somewhere non-standard you will need to set 
> the PKG_CONFIG_PATH before running cmake).
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/question-about-compiling-qpidc-0-22-tp7596813p7598204.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-16 Thread NimbusParc 
+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 though this would
>> technically be an ABI breakage - if it is never set no one can actually
>> be using it for anything useful. Any objections.
> 
> Fine by me, I don't think it is ever used.
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/C-qpid-messaging-MessagingException-detail-tp7597129p7598203.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: How to test Qpid c++ broker ?

2013-09-16 Thread NimbusParc 
+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 form (e.g. image/jpeg or
>>> whatever).
>>
>>> In future there will be an extension to the API (already on trunk, but
>>> won't be released until 0.26), that lets you set the content as an
>>> object (a qpid::types::Variant). That allows the std::string to be
>>> associated with an encoding (utf8, ascii or binary), as well as allowing
>>> it to be a map, list, uuid or one of various numeric types.
>>
>> So, that means the next release (0.26, which is in trunk )already
>> included
>> that sending/receiving the mime type data ??
> 
> Good question. For maps and lists, yes it does (amqp/map and amqp/list 
> respectively). It should also be able to set the text/plain (though at 
> present it does not[1]), and I'll add that straight away. Note that this 
> will be the case only for AMQP 0-10.
> 
> In AMQP 1.0 setting the content-type is discouraged where the content is 
> an AMqpValue section which is how the content 'object' if set will be 
> encoded. You can still send the data as raw bytes with an explicit 
> content type, but to do so you would have to encode it yourself first 
> (at present).
> 
> Note also that the c++ broker will translate between the different 
> encodings. (And in this case a utf8 typed AmqpValue will on conversion 
> to an 0-10 message have text/plain set as the content type).
> 
> [1] https://issues.apache.org/jira/browse/QPID-5090
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/How-to-test-Qpid-c-broker-tp7597435p7598202.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: fyi: qpidc and proton 0.5

2013-09-16 Thread NimbusParc 
+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 next 
> release, i.e. 0.26) will require proton 0.5. The current release (in 
> final phases now), i.e. 0.24, will work with proton 0.4 (or 0.3, but 
> there are some encoding bugs in that one so 0.4 is advised).
> 
> If there are any concerns or questions, please just shout!
> 
> [1] 
> http://mail-archives.apache.org/mod_mbox/qpid-proton/201308.mbox/%3CCACL1BnB-kFdqnbCVkO9xDRkVDJGHZ5V6%2B19wnRnAJmowt1XM0w%40mail.gmail.com%3E
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/fyi-qpidc-and-proton-0-5-tp7597567p7598201.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [python]ImportError: cannot import name ssl

2013-09-16 Thread NimbusParc 
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 results, select package according to your Operating system
(32-bit/64-bit). And then install the package. 

# yum install python-qpid.   (Also include devel packages)

If you don't have epel, first get epel into your yum.repos.d/ and then
install the package. 
Also Make sure that you installed the ssl related packages.
 (For SASL and SSL, include " # yum install cyrus-sasl-devel nss-devel
nspr-devel " )

All the best. 


JustinHan wrote
> Hi,all
> 
> My Python version is:
>> python -V
> Python 2.7.5
> 
> But, when I run the hello example, it indicate me an error:
>> ./hello
> Traceback (most recent call last):
>   File "./hello", line 22, in 
> 
> from qpid.messaging import *
>   File "/home/dchyj/workspace/qpidpy/examples/api/qpid/__init__.py", line
> 20, in 
> 
> import connection
>   File "/home/dchyj/workspace/qpidpy/examples/api/qpid/connection.py",
> line 20, in 
> 
> import datatypes, session
>   File "/home/dchyj/workspace/qpidpy/examples/api/qpid/session.py", line
> 21, in 
> 
> from generator import command_invoker
>   File "/home/dchyj/workspace/qpidpy/examples/api/qpid/generator.py", line
> 22, in 
> 
> from ops import *
>   File "/home/dchyj/workspace/qpidpy/examples/api/qpid/ops.py", line 20,
> in 
> 
> from util import fill
>   File "/home/dchyj/workspace/qpidpy/examples/api/qpid/util.py", line 25,
> in 
> 
> from socket import ssl as wrap_socket
> ImportError: cannot import name ssl
> 
> anyone can tell me what's the reason? thanks in advance!
> 
> Justin





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/python-ImportError-cannot-import-name-ssl-tp7597645p7598200.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-16 Thread NimbusParc 
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 python-qpid

In search results, select package according to your Operating system
(32-bit/64-bit). And then install the package.

# yum install python-qpid.

If you don't have epel, first get epel into your yum.repos.d/ and then
install the package. All the best.


findcomm wrote
> I have installed qpid-0.22 on sles11 sp2 X86_64, the broker works fine.
> But the python client doesn't work, including qpid-config tool and
> qpid-python client test examples.
> When I ran this kind of script, it showed following exception:
> 
> Traceback (most recent call last):
>   File "/usr/local/bin/qpid-config", line 31, in 
> 
> from qpid.messaging import Connection
>   File "/usr/local/lib/python2.7/site-packages/qpid/__init__.py", line 20,
> in 
> 
> import connection
>   File "/usr/local/lib/python2.7/site-packages/qpid/connection.py", line
> 20, in 
> 
> import datatypes, session
>   File "/usr/local/lib/python2.7/site-packages/qpid/session.py", line 26,
> in 
> 
> from ops import Command, MessageTransfer
> ImportError: cannot import name MessageTransfer
> 
> update:
> I have installed qpid-python client and set the env variable.
> PYTHONPATH=/home/zdx/qpid/qpid-0.22/python/:/usr/local/lib/python2.7:/usr/local/lib/python2.7/site-packages
> 
> what is the problem?  thanks





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Help-qpid-python-client-doesn-t-work-for-qpid-0-22-tp7595680p7598199.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-16 Thread NimbusParc 
+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 introduced.
>>
>> However, in the RC3, the qpid-config tool still contains references to
>> flow-to-disk queues. When I try to create one it seems to work fine, the
>> queue is created (i.e. the broker doesn't reject it), but it seems to
>> behave as reject type queue. In the same time the qpid-config doesn't
>> seem
>> to contain any references to creating the queue with the new paging
>> mechanism.
>>
>> Can someone clarify what is the expected situation regarding the old
>> flow-to-disk functionality and the new paging functionality in 0.24?
>> Eventually, how can I configure the queues to use the paged queue
>> functionality?
> 
> The flow to disk policy has been removed (since 0.20), its just that the 
> qpid-config tool has not been updated to reflect that.
> 
> As of 0.24 the paged queue implementation is available as an 
> alternative. There are no 'special' options in qpid-config for that (at 
> least not yet), but you can use the --argument option to create one. E.g.
> 
>qpid-config add queue my-paged-q --argument qpid.paging=True
> 
> You can also use the --argument option to set qpid.max_pages_loaded 
> (which controls how many pages can be in memory at any time) and 
> qpid.page_factor (which controls the page size as a multiple of the 
> platform default page size).
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Flow-to-disk-functionality-and-its-replacement-in-0-24-tp7597697p7598197.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Dynamic routing between disconnected exchanges

2013-09-16 Thread NimbusParc 
+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://qpid.2158936.n2.nabble.com/Dynamic-routing-between-disconnected-exchanges-tp7598100p7598195.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Dynamic routing between disconnected exchanges

2013-09-16 Thread NimbusParc 
Just now i tried this one. Everything works fine for me.
As Ted Ross wrote...

1) Create exchanges 
2) Create dynamic routes 
3) Create queues and bindings 

  After this, just check if all the links are operational or not.
 Then, check in route map that the routes are in bi-directional or not.
 Then check the bindings in between the Exchanges and Queues.
 Then, test by using "spout" and "drain" examples.

Now, you can send messages from A to B, B to C and A to C also. I Think you
may be doing mistake in the bindings.
(i.e) You should bind the queue to the exchange used in dynamic routing. And
separately bind to the same exchange name in another brokers with respected
queues.
 Try freshly by restarting brokers ( take care of the Back up, etc,.) and
follow the sequence. Still if you struggle with the same problem, i'll post
my step-by-step results.
All the best
bacon wrote
> The changes seem to be in what exchange routes end up being created
> however messages are still not making it. Specifically, ./qpid-config
> exchanges -r now looks like this: 
> 
> 
> Exchange '' (direct)
> bind [050aed7f-31c5-4018-ab99-f248b1789573:0.0] =>
> 050aed7f-31c5-4018-ab99-f248b1789573:0.0
> bind [B] => B
> bind
> [qpid.bridge_queue_qpid.tcp:192.168.0.1:5672!test-fanout!test-fanout!_d7ea0855-a1db-451a-bb72-ec61814db3ee]
> =>
> qpid.bridge_queue_qpid.tcp:192.168.0.1:5672!test-fanout!test-fanout!_d7ea0855-a1db-451a-bb72-ec61814db3ee
> bind
> [qpid.bridge_queue_qpid.tcp:192.168.1.2:5672!test-fanout!test-fanout!_d7ea0855-a1db-451a-bb72-ec61814db3ee]
> =>
> qpid.bridge_queue_qpid.tcp:192.168.1.2:5672!test-fanout!test-fanout!_d7ea0855-a1db-451a-bb72-ec61814db3ee
> Exchange 'amq.direct' (direct)
> Exchange 'amq.fanout' (fanout)
> Exchange 'amq.match' (headers)
> Exchange 'amq.topic' (topic)
> Exchange 'test-fanout' (fanout)
> bind [] => B
> bind [] =>
> qpid.bridge_queue_qpid.tcp:192.168.0.1:5672!test-fanout!test-fanout!_d7ea0855-a1db-451a-bb72-ec61814db3ee
> {u'qpid.replicate': u'none', u'qpid.fed.origin':
> u'd7ea0855-a1db-451a-bb72-ec61814db3ee', u'qpid.fed.op': u'',
> u'qpid.fed.tags': u'd7ea0855-a1db-451a-bb72-ec61814db3ee'}
> bind [] =>
> qpid.bridge_queue_qpid.tcp:192.168.1.2:5672!test-fanout!test-fanout!_d7ea0855-a1db-451a-bb72-ec61814db3ee
> {u'qpid.replicate': u'none', u'qpid.fed.origin':
> u'd7ea0855-a1db-451a-bb72-ec61814db3ee', u'qpid.fed.op': u'',
> u'qpid.fed.tags': u'd7ea0855-a1db-451a-bb72-ec61814db3ee'}
> Exchange 'qmf.default.direct' (direct)
> Exchange 'qmf.default.topic' (topic)
> bind [direct.8cd9ca02-a36d-413d-ac09-a2d5a9feb534] =>
> 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 manually setting up static exchange
> routes (actually, I've tried that but didn't get far). 
> 
>  -Andrew
> 
> 
> 
> 
> 
> On Sep 13, 2013, at 1:33 AM, "NimbusParc [via Qpid]" <

> ml-node+s2158936n7598155h82@.nabble

> > wrote:
> 
>> -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 
>> > 
>> >===
>> > 
>> >  direct   3 0  0   00  
>> 00 
>> >  amq.direct  direct   Y   076 76   0 34.7k  
>> 34.7k   0 
>> >  amq.fanout  fanout   Y   0 0  0   00  
>> 00 
>> >  amq.match   headers  Y   0 0  0   00  
>> 00 
>> >  amq.topic   topicY   0 0  0   00  
>> 00 
>> >  test-topictopic2 3  2   1   12  
>> 84  <--- (drop is 1 after attempt to sent to c) 
>> >  qmf.default.direct  direct   0 9  9   0 2.40k  
>> 2.40k   0 
>> >  qmf.default.topic   topic1   333  7 326  255k  
>> 17.2k 238k 
>> >  qpid.management topi

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

2013-09-13 Thread NimbusParc 
+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 the URL parameter, to trigger the reconnect
>>> based on the URL which was specified when creating the connection.
>>
>> Yes, that sounds like a good idea. I'll update the patch to do that.
>> Thanks!
> 
> Fyi: I've updated the patch on reviewboard to add this method. Also 
> changed the name of getCurrentUrl() to getUrl() as Alan suggested.
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/c-give-application-more-direct-control-over-reconnect-replay-tp7597590p7598163.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Increasing number of messages normal?

2013-09-13 Thread NimbusParc 
+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 and route them to the management exchanges. However if there is
>>> no-one subscribed to receive those events, then they will just be
>>> dropped.
>>>
>>> Using qpid-stat will itself trigger the raising of events on the broker
>>> (connection opened and closed, queues created and destroyed etc).
>>> Furthermore I believe there is some periodic 'publishing' of current
>>> object
>>> stats which again may well just be dropped.
>>>
>>> Ideally these stats related to management itself would be hidden by
>>> default
>>> of course.
>>  From what you write, it sounds like its probably safe to ignore them.
>> Good.
> 
> What Gordon says is true.  Those are internally generated management and 
> status updates that there is no subscriber for.
> 
>>
>> Nevertheless if time permits, I may try to connect with a dummy-client
>> to the exchanges that cause high message drops and look into what
>> those messages are. We will deploy the application into live operation
>> in a few month and I would rather be on the safe side there. ;-)
> 
> If you run qpid-tool, it will subscribe to the updates.  The 
> qpid-printevents utility will subscribe to (and display) the events.
> 
> -Ted
> 
>>
>> Thanks,
>> Christian
>>
>> -
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache

>>
> 
> 
> -
> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

> For additional commands, e-mail: 

> users-help@.apache





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Increasing-number-of-messages-normal-tp7598083p7598161.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [ANNOUNCE] Apache Qpid 0.24 released

2013-09-13 Thread NimbusParc 
+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 brokers written in 
>C++ and Java, along with clients for C++, Java JMS, .Net, Python, 
>Ruby, and Perl. 

>Qpid 0.24 is available from our website: 

> http://qpid.apache.org/download.html

>The 0.24 release includes many bug fixes and improvements.  We 
>recommend that all users upgrade.  A comprehensive list of changes in 
>the 0.24 release is available here: 

> http://qpid.apache.org/releases/qpid-0.24/release-notes.html




--
View this message in context: 
http://qpid.2158936.n2.nabble.com/ANNOUNCE-Apache-Qpid-0-24-released-tp7597972p7598159.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

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

2013-09-13 Thread NimbusParc 
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 Gordon, it seemed to me that
>> the qpid-cpp sources probably shouldn't even include the Perl, or other
>> language, bindings. Instead it should probably only carry the C++ client
>> and server code, and leave the bindings to the monolithic tarball that's
>> produced instead.
>> 
>> So my question is this, should we trim what's included in the qpid-cpp
>> sources to be only the C++ client and server code, leaving the language
>> bindings for the separate source tarballs?
>> 
>> [ ] Yes, remove the language bindings from qpid-cpp-${VER}
>> [ ] No, leave the language bindings in qpid-cpp-${VER}
>> 
>> 
>> [1] http://www.apache.org/dyn/closer.cgi/qpid/0.24/qpid-cpp-0.24.tar.gz
>> [2] http://issues.apache.org/jira/browse/QPID-5128
> 
> To clarify, since it may not be clear, I'm not asking to remove the
> bindings from the qpid-${VER} file (the "monolithic tarball" mentioned
> above), but removing them from the qpid-cpp tarball.
> 
> -- 
> Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
> Delivering value year after year.
> Red Hat ranks #1 in value among software vendors.
> http://www.redhat.com/promo/vendor/
> 
> 
> 
> attachment0 (205 bytes)
> ;





--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Removing-the-bindings-from-qpid-cpp-source-tarball-tp7598078p7598157.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Increasing number of messages normal?

2013-09-13 Thread NimbusParc 
--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-tp7598083p7598156.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Dynamic routing between disconnected exchanges

2013-09-13 Thread NimbusParc 
-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
> 
> >===
>  direct   3 0  0   00  
> 00
>  amq.direct  direct   Y   076 76   0 34.7k  
> 34.7k   0
>  amq.fanout  fanout   Y   0 0  0   00  
> 00
>  amq.match   headers  Y   0 0  0   00  
> 00
>  amq.topic   topicY   0 0  0   00  
> 00
>  *test-topictopic2 3  2   1   12  
> 84  <--- (drop is 1 after attempt to sent to c) *
>  qmf.default.direct  direct   0 9  9   0 2.40k  
> 2.40k   0
>  qmf.default.topic   topic1   333  7 326  255k  
> 17.2k 238k
>  qpid.management topic0 0  0   00  
> 00


In the above output it is very clear in the stats of "bytesDrop".
>
>Thought: It seems that A doesn't know anything a about C or c so it drops
the message... could this have something to do
>with using a topic exchange? Or should B be telling A what it knows about C
(but isn't)? 
>

   Try once with fanout exchange instead of topic exchange and let me know
whether any change will be there are not ? 



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Dynamic-routing-between-disconnected-exchanges-tp7598100p7598155.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Create a collection of topics

2013-09-13 Thread NimbusParc 
-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 chosen by the need for subscribers 
>to filter on particular subtopics or to dynamically create distinct
topics].

+1



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Create-a-collection-of-topics-tp7597987p7598154.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [ANNOUNCE] Apache Qpid 0.24 released

2013-09-13 Thread NimbusParc 
+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 brokers written in 
>C++ and Java, along with clients for C++, Java JMS, .Net, Python, 
>Ruby, and Perl. 

>Qpid 0.24 is available from our website: 

> http://qpid.apache.org/download.html

>The 0.24 release includes many bug fixes and improvements.  We 
>recommend that all users upgrade.  A comprehensive list of changes in 
>the 0.24 release is available here: 

> http://qpid.apache.org/releases/qpid-0.24/release-notes.html




--
View this message in context: 
http://qpid.2158936.n2.nabble.com/ANNOUNCE-Apache-Qpid-0-24-released-tp7597972p7598153.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid 0.24

2013-09-02 Thread NimbusParc 
  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 Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Any one have compiled qpid on Pidora?

2013-08-20 Thread NimbusParc 
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 the Apache Qpid users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: tcp-nodelay on broker

2013-08-20 Thread NimbusParc 
-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 unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: tcp-nodelay on broker

2013-08-20 Thread NimbusParc 
   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 mailing list archive at Nabble.com.

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

2013-08-20 Thread NimbusParc 
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   *./setup.py install * (as Super User)  Now, you won't
get any exceptions.




--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Help-qpid-python-client-doesn-t-work-for-qpid-0-22-tp7595680p7597116.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.