On Wed, 2017-03-01 at 18:06 +0100, Rob Godfrey wrote:
> On 1 March 2017 at 17:53, Kai Hudalla wrote:
>
> > On Wed, 2017-03-01 at 15:44 +, Robbie Gemmell wrote:
> > > On 1 March 2017 at 15:29, Kai Hudalla wrote:
> > > > On Wed, 2017-03-01 at
Hi,
Based on http://qpid.apache.org/proton/overview.html (and
http://qpid.apache.org/proton/), I'm looking for the JavaScript
implementation.
The only think I can find are JavaScript bindings that are
cross-compiled from the C version using Emscripten:
On Wed, 2017-03-01 at 17:04 +, Gordon Sim wrote:
> On 01/03/17 16:53, Kai Hudalla wrote:
> > If the sender has e.g. 100 credits left and
> > indeed has content to send 100 messages then a drain doesn't prevent him
> > from
> > sending all 100 messages. However, flowing 0 link-credit to the
On 1 March 2017 at 22:22, Gordon Sim wrote:
> On 01/03/17 21:18, Rob Godfrey wrote:
>
>> My gut feeling says that the library (Proton) should detect the error if
>> it
>> can determine that the other party has sent beyond any limit it might
>> possibly still believe to be
On 01/03/17 21:18, Rob Godfrey wrote:
My gut feeling says that the library (Proton) should detect the error if it
can determine that the other party has sent beyond any limit it might
possibly still believe to be true... which (in the simplest form) might
just mean retaining a high watermark of
On 1 March 2017 at 22:13, Gordon Sim wrote:
> On 01/03/17 21:09, Rob Godfrey wrote:
>
>> On 1 March 2017 at 19:28, Gordon Sim wrote:
>>
>> On 01/03/17 18:14, Rob Godfrey wrote:
>>>
>>> The link credit is an absolute value on the wire... but proton presents
On 01/03/17 21:09, Rob Godfrey wrote:
On 1 March 2017 at 19:28, Gordon Sim wrote:
On 01/03/17 18:14, Rob Godfrey wrote:
The link credit is an absolute value on the wire... but proton presents it
in relative terms. If you had 500 units of credit outstanding and
flow(-500)
On 1 March 2017 at 19:28, Gordon Sim wrote:
> On 01/03/17 18:14, Rob Godfrey wrote:
>
>> The link credit is an absolute value on the wire... but proton presents it
>> in relative terms. If you had 500 units of credit outstanding and
>> flow(-500) and then flow(2), and you get 5
Without the "name" field the ACL rule applies to "AMQP 1.0 establish sender
link to queue" and not to AMQP 0-10 publishing to an exchange.
See the table
On 1 March 2017 at 20:25, Olivier Mallassi
wrote:
> Rob, all
>
> Thank you rob for this. Could you please share more details regarding not
> using the "/"?
>
>
So there are a couple of reasons why I think not using a / makes sense:
1) Because of exactly the REST /
Hello Ganesh,
It seems that "zip" files are not allowed and thus my mail is never getting
delivered.
You can get it from here: http://www.filedropper.com/test_210
Regards,
Adel
From: Adel Boutros
Sent: Wednesday, March 1, 2017 9:09:29 PM
To:
Hi Adel,
I sent you a subsequent email asking you for the log files. Did you already
respond to that email? For some reason, I am not seeing your response. I see
only your first response where you attached the output of PN_TRACE_FRM=1
Can you please resend the log files?
Sorry, Thanks.
Hello Ganesh,
Did you have any luck with what I sent you?
Regards,
Adel
From: Adel Boutros
Sent: Wednesday, March 1, 2017 9:56:44 AM
To: users@qpid.apache.org
Subject: Re: [Qpid Dispatch - 0.7.0] Random failure on unit test
"system_tests_link_routes" on
Hi Morgan,
You might be missing the exchange name. The publish rule should look
something like this:
acl allow producer publish exchange name=my_exchange routingkey=myRoutingKey
But without the logs it is just guessing.
Jakub
On Wed, Mar 1, 2017 at 8:13 PM, Morgan Lindqvist <
Rob, all
Thank you rob for this. Could you please share more details regarding not
using the "/"?
On our side we are using amqp 1.0 that, AFAIU, promotes the "complex"
addressing plans
The benefit for us would be
- alignements between our http and amqp naming conventions. It is a nice to
have
Hi All,
I have an issue that I can not get working
Setup:
I have one exchange and three queues connected to it with a filter between
the exchange and each queue.
The issue I have is to get the users write access to the exchange.
acl allow producer access exchange name=nwEx
acl allow producer
On 01/03/17 18:14, Rob Godfrey wrote:
The link credit is an absolute value on the wire... but proton presents it
in relative terms. If you had 500 units of credit outstanding and
flow(-500) and then flow(2), and you get 5 messages on the wire arriving
after that point... what state is your link
On 1 March 2017 at 18:49, Gordon Sim wrote:
> On 01/03/17 17:19, Robbie Gemmell wrote:
>
>> How did you know they had actually stopped or that it was then safe to
>> flow them new credit, just waiting for a while?
>>
>> If you flow new credit before the link is actually stopped
On 01/03/17 17:19, Robbie Gemmell wrote:
How did you know they had actually stopped or that it was then safe to
flow them new credit, just waiting for a while?
If you flow new credit before the link is actually stopped you need to
cope with that fairly specifically in case they hadnt really
Hi Tim,
Please find attached a sample application testing transaction
throughput for one publishing and one consuming connections.
By running it on my machine I see a difference in performance of ~15%
between 0.11.0 and 0.20.0.
Our performance test suite uses 10 publishing and 10 consuming
On 1 March 2017 at 16:47, Gordon Sim wrote:
> On 01/03/17 16:07, Robbie Gemmell wrote:
>>
>> The are issues around delivery count handling and the credit due to in
>> flight messages and how thats handled. It also requires echo support
>> (which proton lacks, theres another JRIA
In general I'd advise against using the '/' character in queue names if
possible... however if you must, then you need double encode the name, so
"a/b" would become "a%252Fb"
Hope this helps,
Rob
On 1 March 2017 at 17:31, Antoine Chevin wrote:
> Hello,
>
> I created a
On 1 March 2017 at 18:04, Gordon Sim wrote:
> On 01/03/17 16:53, Kai Hudalla wrote:
>
>> If the sender has e.g. 100 credits left and
>> indeed has content to send 100 messages then a drain doesn't prevent him
>> from
>> sending all 100 messages. However, flowing 0 link-credit to
On 1 March 2017 at 17:53, Kai Hudalla wrote:
> On Wed, 2017-03-01 at 15:44 +, Robbie Gemmell wrote:
> > On 1 March 2017 at 15:29, Kai Hudalla wrote:
> > > On Wed, 2017-03-01 at 15:07 +, Robbie Gemmell wrote:
> > > > On 1 March 2017 at
On Wed, 2017-03-01 at 15:44 +, Robbie Gemmell wrote:
> On 1 March 2017 at 15:29, Kai Hudalla wrote:
> > On Wed, 2017-03-01 at 15:07 +, Robbie Gemmell wrote:
> > > On 1 March 2017 at 14:31, Kai Hudalla wrote:
> > > > Hi,
> > > >
> > > > we
On 01/03/17 16:07, Robbie Gemmell wrote:
The are issues around delivery count handling and the credit due to in
flight messages and how thats handled. It also requires echo support
(which proton lacks, theres another JRIA I raised for that) to do
properly, and you essentially need to remember
Hello,
I created a queue with a '/' in the name. How can I access it in the rest
api?
I tried to encode the '/' with %2F but I still get a 422 "too many entries
in path for REST servlet queue."
Can you please help?
Regards,
Antoine
On 1 March 2017 at 16:08, Rob Godfrey wrote:
> On 1 March 2017 at 16:56, Gordon Sim wrote:
>
>> On 01/03/17 15:37, Gordon Sim wrote:
>>
>>> On 01/03/17 14:31, Kai Hudalla wrote:
>>>
Assuming that we have a link established between a Receiver (r) and
On 1 March 2017 at 16:56, Gordon Sim wrote:
> On 01/03/17 15:37, Gordon Sim wrote:
>
>> On 01/03/17 14:31, Kai Hudalla wrote:
>>
>>> Assuming that we have a link established between a Receiver (r) and a
>>> Sender (s)
>>> with a current link-credit of 4 and a delivery count of
The are issues around delivery count handling and the credit due to in
flight messages and how thats handled. It also requires echo support
(which proton lacks, theres another JRIA I raised for that) to do
properly, and you essentially need to remember you reduced the credit
to handle the state
Thanks, setting amqp.idleTimeout=0 works.
On Tue, Feb 14, 2017 at 12:04 PM Rob Godfrey
wrote:
> On 14 February 2017 at 20:11, Robbie Gemmell
> wrote:
>
> > On 14 February 2017 at 18:07, Benjamin Busjaeger
> > wrote:
> > >
On 01/03/17 15:37, Gordon Sim wrote:
On 01/03/17 14:31, Kai Hudalla wrote:
Assuming that we have a link established between a Receiver (r) and a
Sender (s)
with a current link-credit of 4 and a delivery count of 20 on both sides.
When invoking r.flow(6), the given credit (6) is _added_ to the
On 1 March 2017 at 15:44, Robbie Gemmell wrote:
> On 1 March 2017 at 15:29, Kai Hudalla wrote:
>> On Wed, 2017-03-01 at 15:07 +, Robbie Gemmell wrote:
>>> On 1 March 2017 at 14:31, Kai Hudalla wrote:
>>> > Hi,
>>> >
On 1 March 2017 at 15:43, Rob Godfrey wrote:
> On 1 March 2017 at 16:29, Kai Hudalla wrote:
>
>> On Wed, 2017-03-01 at 15:07 +, Robbie Gemmell wrote:
>> > On 1 March 2017 at 14:31, Kai Hudalla wrote:
>> > > Hi,
>> > >
On 1 March 2017 at 15:29, Kai Hudalla wrote:
> On Wed, 2017-03-01 at 15:07 +, Robbie Gemmell wrote:
>> On 1 March 2017 at 14:31, Kai Hudalla wrote:
>> > Hi,
>> >
>> > we are working on the Eclipse Hono project where we use vertx-proton and
>> >
On 1 March 2017 at 16:29, Kai Hudalla wrote:
> On Wed, 2017-03-01 at 15:07 +, Robbie Gemmell wrote:
> > On 1 March 2017 at 14:31, Kai Hudalla wrote:
> > > Hi,
> > >
> > > we are working on the Eclipse Hono project where we use vertx-proton
>
On 01/03/17 14:31, Kai Hudalla wrote:
Assuming that we have a link established between a Receiver (r) and a Sender (s)
with a current link-credit of 4 and a delivery count of 20 on both sides.
When invoking r.flow(6), the given credit (6) is _added_ to the receiver's
current credit resulting in
On Wed, 2017-03-01 at 15:07 +, Robbie Gemmell wrote:
> On 1 March 2017 at 14:31, Kai Hudalla wrote:
> > Hi,
> >
> > we are working on the Eclipse Hono project where we use vertx-proton and
> > (implicitly) proton-j under the hood for exchanging large amounts of
> >
Thank you for the explanation. It is very helpful to understand the
combination of Authentication Provider and Group Provider. I think we use
LDAP and / or SAML so I am interested in the fact that the UAA is an OAuth2
server in front of other authentication sources. I figured out what URLs I
need
On 1 March 2017 at 14:31, Kai Hudalla wrote:
> Hi,
>
> we are working on the Eclipse Hono project where we use vertx-proton and
> (implicitly) proton-j under the hood for exchanging large amounts of messages
> using AMQP 1.0.
>
> During our tests I stumbled across the way
Hi,
we are working on the Eclipse Hono project where we use vertx-proton and
(implicitly) proton-j under the hood for exchanging large amounts of messages
using AMQP 1.0.
During our tests I stumbled across the way that proton-j seems to handle link-
credit being exchanged via FLOWs.
My
Hello Dan,
I cannot comment too much on what you have to do on the CloudFoundry
(CF) side of things but I might be able to give some advice from the
Qpid Broker for Java side.
For authentication, the broker supports OAuth2 [1] which is also
supported by CF [2]. Qpid uses the implicit grant
42 matches
Mail list logo