Hi Everyone,
I've put together an alpha 2 for Proton 0.9. I believe the memory issues
identified in alpha 1 are addressed. Source and binaries are posted in the
usual locations:
Source artifacts:
http://people.apache.org/~rhs/qpid-proton-0.9-alpha-2/
Java binaries:
https://repository.apac
Hi Rob,
Thanks for looking at this. We'll probably continue using single-queue
consumers for now then, since the fair behavior is important to us, and try
using multiple-queue consumers again when the new threading model is
available.
Thanks,
Helen
On Tue, Jan 20, 2015 at 10:32 AM, Rob Godfrey
Hello!
I am trying to build Qpid 0.28 on a Solaris Sparc 10 machine, but the build
failes when trying to compile the python wrappers. I have python 2.4, 2.6
and 2.7 installed on the machine. The Swig Version is 2.0.9.
Can you give me some hints what I could try next?
Best regards
Raphael
make o
Hi Justin
I'm in agreement with the plan to reorganise the source tree in the way you
describe (and expect that we would want a similar change for java) but am I
concerned about the timing of such a big change.We should be
reorganising trunk just *after* a release branch to give us plenty of t
On 01/23/2015 01:53 PM, Alan Conway wrote:
I'm trying to determine if the message header x-amqp-to has any use or
if it's a historical leftover. Here's what I found in the 3 qpid
projects:
== proton
== dispatch
doc/book/release-0.1.md:request.setProperty("x-amqp-to",
"amqp:/_local/$manag
I'm trying to determine if the message header x-amqp-to has any use or
if it's a historical leftover. Here's what I found in the 3 qpid
projects:
== proton
== dispatch
doc/book/release-0.1.md:request.setProperty("x-amqp-to",
"amqp:/_local/$management");
doc/book/using.md:request.se
Hi Gordon,
thanks a million, just tried it out and it worked like a charm!
Cheers,
Daniel
2015-01-22 18:31 GMT+01:00 Gordon Sim :
> On 01/22/2015 04:32 PM, Daniel Wenske wrote:
>
>> I switched on the qpid library logging and can see the properties are
>> there. It shows the following:
>>
>
