Thanks Cliff, that fixed it.
-Original Message-
From: Cliff Jansen [mailto:cliffjan...@gmail.com]
Sent: Wednesday, November 06, 2013 2:14 PM
To: users@qpid.apache.org
Subject: Re: SSL support in org.apache.qpid.messaging .NET API
Albert,
Please try the recent fix to the JIRA (r1539474).
Hi Gordon & everyone else,
I finally managed to spent some quality time with the queue paging today. I
have quite a lot of questions / comments / feedback. I hope you don't mind.
If you want, I can as usually rise the JIRAs or provide more details for
reproducing of the problems. Just let me know
Albert,
Please try the recent fix to the JIRA (r1539474). This should get you
going for the 0-10 protocol.
Cliff
On Wed, Nov 6, 2013 at 10:20 AM, Albert Pomortsev wrote:
> Chuck,
>
> I created https://issues.apache.org/jira/browse/QPID-5302
>
> Thanks,
> Albert.
>
> -Original Message-
Chuck,
I created https://issues.apache.org/jira/browse/QPID-5302
Thanks,
Albert.
-Original Message-
From: Chuck Rolke [mailto:cro...@redhat.com]
Sent: Wednesday, October 30, 2013 6:57 AM
To: users@qpid.apache.org
Subject: Re: SSL support in org.apache.qpid.messaging .NET API
Hi Albert,
I created a JIRA QPID-5300 for this one as well. Although I guess this is
not a big issue.
Thanks & Regards
Jakub
On Wed, Nov 6, 2013 at 2:48 PM, Gordon Sim wrote:
> On 11/06/2013 01:35 PM, Jakub Scholz wrote:
>
>> Hi,
>>
>> It seems when some ACL errors occur, the C++ broker is sometimes usin
Hi Gordon,
Thanks for your answer - I entered it as QPID-5299.
Thanks & Regards
Jakub
On Wed, Nov 6, 2013 at 2:46 PM, Gordon Sim wrote:
> On 11/06/2013 12:59 PM, Jakub Scholz wrote:
>
>> Hi,
>>
>> When a client is connecting with AMQP 1.0 to the C++ broker and the node
>> from which it wants
On 11/06/2013 01:35 PM, Jakub Scholz wrote:
Hi,
It seems when some ACL errors occur, the C++ broker is sometimes using the
AMQP 1.0 error code unauthorized-access and sometimes internal-error. For
example the "ACL denied queue access" error is amqp:unauthorized-access:
[0x24ca9d0:0] <- @detach
On 11/06/2013 12:59 PM, Jakub Scholz wrote:
Hi,
When a client is connecting with AMQP 1.0 to the C++ broker and the node
from which it wants to consume messages doesn't exist, the broker throws an
amqp:not-found error even when ACL rules deny the user to access or publish
from the given node (qu
Hi,
It seems when some ACL errors occur, the C++ broker is sometimes using the
AMQP 1.0 error code unauthorized-access and sometimes internal-error. For
example the "ACL denied queue access" error is amqp:unauthorized-access:
[0x24ca9d0:0] <- @detach [handle=0, closed=true, error=@error
[conditio
Hi,
When a client is connecting with AMQP 1.0 to the C++ broker and the node
from which it wants to consume messages doesn't exist, the broker throws an
amqp:not-found error even when ACL rules deny the user to access or publish
from the given node (queue).
For a security reasons, I would assume
10 matches
Mail list logo