I think it is related to proton because the exact same messages using the exact
same credentials are processed by an AMQPlite client running at the same time.
I am assuming it is related to how the message is constructed because an error
that affected all ServiceBus clients should have been
The C++ broker also doesn't have any problems with 10MB messages. we use
them quite regularly (including persistence). I'm not 100% sure what is the
maximal limit, but I usually start getting careful around 100MB. The reason
for that is not always only the broker, but also the clients which need
Thanks Rob
Anyone with some C++ specific information?
From: Rob Godfrey [rob.j.godf...@gmail.com]
Sent: Thursday, February 25, 2016 4:20 PM
To: users@qpid.apache.org
Subject: Re: Gneral Question: Does QPID a message size limit?
Each different component
On Thu, 2016-02-25 at 21:16 +, Gordon Sim wrote:
> On 25/02/16 16:01, Randy Armstrong wrote:
> >
> > [00B3D578]:0 <- @detach(22) [handle=0, closed=true, error=@error(29
> > )
> > [condition=:"amqp:unauthorized-access", description="Unauthorized
> > access.
> > 'Listen' claim(s) are required
In the function:
pni_process_mechanisms(pn_transport_t *transport, const char *mechs)
mechs = MSSBCBS PLAIN ANONYMOUS EXTERNAL
transport->sasl->username and transport->sasl->password are correct.
EXTERNAL is selected because it is first to be tested in the function.
I changed the order so PLAIN
Each different component of Qpid may have different limitations. As far as
the Java Broker goes (and the Java AMQP 0-8/0-9/0-9-1/0-10 client - since
they share a common underlying library) the theoretical message size limit
is 2GB. By default the Java Broker rejects messages over 500MB in size,
At a client site working on the adoption of QPID.
The question that has been asked is if QPID can handle messages in the 10 MB
size range.
Is there a documented message size limit anywhere? Is the size system resource
dependent?
Thanks for your inputs it is welcomed and appreciated.
On 25/02/16 16:01, Randy Armstrong wrote:
[00B3D578]:0 <- @detach(22) [handle=0, closed=true, error=@error(29)
[condition=:"amqp:unauthorized-access", description="Unauthorized access.
'Listen' claim(s) are required to perform this operation. Resource:
Thank-you for the additional information.
It appears that you successfully create an SSL encrypted TCP
connection acceptable to each peer. So SSL configuration seems fine.
It further appears that the service bus refuses to create a link to
your topic based on an unauthorized access attempt,
Hi Paul,
I work with a set of customers that set this kind of thing up as a set of
meshed brokers with federation links that both load balances and acts as a
mechanism of high availability.
-Steve Huston
> -Original Message-
> From: Flores, Paul A. [mailto:paul.a.flo...@saic.com]
>
At a client site evaluating aspects of QPID for adoption for its use in a
mission critical application.
This is one question / area I was asked to elicit information regarding current
capabilities, plans and alternatives.
Has anyone looked at either the distributed broker functionality and
On 24/02/16 19:03, Andrew Stitcher wrote:
On Wed, 2016-02-24 at 06:15 -0800, Justin Ross wrote:
...
This actually goes quite far beyond what I was expecting before the
upcoming cpp etc releases, looks like you have been busy! :)
Seconded - I'm really impressed with how far you have taken
I am using the "recv" example from the 0.12 codebase.
The URL I am using is:
amqps://receiver:@opcfoundation-prototyping.servicebus.windows.net/MyTopic/Subscriptions/
default"
I have tried with
pn_messenger_set_flags(messenger, PN_FLAGS_ALLOW_INSECURE_MECHS);
and
On Wed, 2016-02-24 at 13:52 -0500, Ken Giusti wrote:
> Hrm - where did libqpid-proton-cpp.* files come from? I don't
> recognize any proton library that has that -cpp suffix.
Those are the new C++ binding, which I think implies you have installed
proton 12.0 or master at some point as they
On 25/02/16 12:34, Filipe Santos wrote:
Hi
I’m experiencing the error “Frame too large for buffer.” from Qpid
broker version 0.32.
This was already discussed here last April and the following issue was
raised:
https://issues.apache.org/jira/browse/QPID-6501
Does anyone knows if this is
FYI: I am able to successfully compile qpid-proton0.11.1 with absolutely no
issues /problems.
From: Flores, Paul A. [paul.a.flo...@saic.com]
Sent: Thursday, February 25, 2016 8:29 AM
To: users@qpid.apache.org
Subject: RE: Help -> QPID Proton 12.0 build
It is not a compiler directive that is at the root cause of this error message
as it is persistent.
It is not the gcc compiler version (gcc (GCC) 4.1.2 20080704 (Red Hat
4.1.2-55)).
When I do a "make -k" I see a large number of warnings, granted most have to do
with the generation of
There were 5 binding and 1 non-binding +1 votes, and no other votes
received. The vote has passed.
Voting thread:
http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-Java-6-0-1-RC3-td7638867.html
I am going to publish release artifacts into dist release repo and
maven repo. After that I will
There were 5 binding and 1 non-binding +1 votes, and no other votes
received. The vote has passed.
Kind Regards,
Alex
On 22 February 2016 at 11:51, Oleksandr Rudyy wrote:
> Hi everyone,
>
> I created a new 6.0.1 RC3 build containing a fix for a blocker:
>
> QPID-6817 - [Java
+1
On 22 February 2016 at 11:51, Oleksandr Rudyy wrote:
> Hi everyone,
>
> I created a new 6.0.1 RC3 build containing a fix for a blocker:
>
> QPID-6817 - [Java Broker] On abrupt connection close from client side when
> Broker is delivering messages to consumer, the delivering
Hi
I'm experiencing the error "Frame too large for buffer." from Qpid broker
version 0.32.
This was already discussed here last April and the following issue was raised:
https://issues.apache.org/jira/browse/QPID-6501
Does anyone knows if this is already fixed for version 0.34? Or will it be
If you want to disable the c++ binding, you can use the cmake flag
-DBUILD_CPP=FALSE.
Alexandre
On mer., 2016-02-24 at 22:11 +, Robbie Gemmell wrote:
> I'd expected the error message and context (older OS/compiler) being
> the same might make it applicable.
>
> Its building the C++ binding
22 matches
Mail list logo