Re: (java qpid) when consumer stoped but producer send msg all the time,cause memory not enough

Which version (0.30, 0.32, 6.0) of the Java Broker are you using? How much memory (-Xmx) are you giving the broker? What persistent store are you using? How many messages are you expecting the broker to hold while the consumer is stopped? The documentation gives guidance on flow to disk, and

Re: Please update appveyor.yml version [Was: Proton 0.12.0 release update - Alpha is available]

Can I suggest a more basic change of simply removing the release version from the Appveyor job id? None of the other CI jobs have that, and given it has been wrong for around 5 months it doesn't seem particularly noted by most folks. The branch name could still be there as it is now, which in

Re: Request delay of proton 0.12 beta.

Okay, not a problem. I'll adjust the schedule on the release page. Justin On Tue, Jan 19, 2016 at 11:57 AM, Alan Conway wrote: > We are working hard on the C++ binding, which will include a > "connection_engine" as an alternative to the reactor, I'll post another > note on

Re: Several issues with the Java Broker

Thx for the answer. Im using the newest qpid messaging api (c++), v0.34 together with the newest Java broker (6.0.0). The protocol is AMQP 0-10. I'm afraid that I can't generate a protocol trace with the c++ api, right? But indeed the startup phase of the broker seems to be the problem. If it's

Re: federated broker system - end-to-end messaging not working

On 01/19/2016 07:56 PM, jjw tectec wrote: Thanks Gordon. Adding the link option worked. However, even after msg.setProperty("x-amqp-0-10.routing-key", "keyX"); // publisher msg.getProperties()["x-amqp-0-10.routing-key"].asString() is still the queue name, not "keyX" (at the subscriber); Is

Re: Several issues with the Java Broker

On 01/19/2016 06:29 PM, rat...@web.de wrote: I can't generate a protocol trace with the c++ api run your program with QPID_LOG_ENABLE=trace+ - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands,

Re: federated broker system - end-to-end messaging not working

On 01/19/2016 05:23 PM, jjw tectec wrote: Hi Gordon, Yes, changing the key name to queue name made messages flow end-to-end. I had also suspected that the routing key wasn't set the way I wanted it be. So I had tried to set and get routing-key property at the client sides: publisher:

Re: federated broker system - end-to-end messaging not working

Thanks Gordon. Adding the link option worked. However, even after msg.setProperty("x-amqp-0-10.routing-key", "keyX"); // publisher msg.getProperties()["x-amqp-0-10.routing-key"].asString() is still the queue name, not "keyX" (at the subscriber); Is this an expected behavior? Thank you! jjw

Re: federated broker system - end-to-end messaging not working

Ok, thank you so much! On Tue, Jan 19, 2016 at 1:58 PM, Gordon Sim wrote: > On 01/19/2016 07:56 PM, jjw tectec wrote: > >> Thanks Gordon. Adding the link option worked. However, even after >> >> msg.setProperty("x-amqp-0-10.routing-key", "keyX"); // publisher >> >>

getTtl() behaviour (C++ messaging API)

Hi, I have some questions about the value from qpid::messaging::Message::getTtl() on received messages; based on testing, I've concluded that 1. The value returned represents the time that remains of the time-to-live specified by the sender. 2. If no TTL was set, the value is

Re: Please update appveyor.yml version [Was: Proton 0.12.0 release update - Alpha is available]

On Tue, 2016-01-19 at 10:39 +, Robbie Gemmell wrote: > Can I suggest a more basic change of simply removing the release > version from the Appveyor job id? > > None of the other CI jobs have that, and given it has been wrong for > around 5 months it doesn't seem particularly noted by most

Request to include fix for PROTON-1088 in Qpid-Proton release 0.12.0

Hello All, I have a fix for https://issues.apache.org/jira/browse/PROTON-1088 and this fix needs to be in Proton 0.12.0 but did not make it to the alpha release Here are the commits (2 commits because I forgot to include the SSL stubs in the first commit) (thanks kgiusti and astitcher) (1)

Re: getTtl() behaviour (C++ messaging API)

On 01/19/2016 02:19 PM, Toralf Lund wrote: Hi, I have some questions about the value from qpid::messaging::Message::getTtl() on received messages; based on testing, I've concluded that 1. The value returned represents the time that remains of the time-to-live specified by the sender. 2.

Re: Please update appveyor.yml version [Was: Proton 0.12.0 release update - Alpha is available]

On 19 January 2016 at 15:25, Andrew Stitcher wrote: > On Tue, 2016-01-19 at 10:39 +, Robbie Gemmell wrote: >> Can I suggest a more basic change of simply removing the release >> version from the Appveyor job id? >> >> None of the other CI jobs have that, and given it has

Re: federated broker system - end-to-end messaging not working

Hi Gordon, Yes, changing the key name to queue name made messages flow end-to-end. I had also suspected that the routing key wasn't set the way I wanted it be. So I had tried to set and get routing-key property at the client sides: publisher: msg.setProperty("x-amqp-0-10.routing-key", "keyX");