Hello Qpid Proton users!
I have this (new) question.
Assuming I have a pn_data_t* containing 2 nodes, how can I get
a pn_data_t* that represents *only* the first node?
Best Regards,
Andrei Porumb
On Thu, 2015-03-12 at 09:55 +, Chris Richardson wrote:
> Not sure if this will turn out to be helpful or spam but I've previously
> encountered this error message and added the following to our kb:
>
> This is related to an invalid SSL certificate and has been observed in a
> situation where t
Ah I think I misunderstood earlier then hehe.
I'd agree that if its long standing we should defer to a 0.32.1 point
release, unless something else comes up that requires a respin in
which case I would include it.
Robbie
On 12 March 2015 at 16:41, Timothy Bish wrote:
> I wouldn't treat it as a b
I wouldn't treat it as a blocker for the release, I'm pretty sure this
has been popping up in our CI for some time now.
On 03/12/2015 12:36 PM, Rob Godfrey wrote:
>From looking at the code I don't think this is a new issue... I think
the same deadlock path would have been present in 0.30 and pr
>From looking at the code I don't think this is a new issue... I think
the same deadlock path would have been present in 0.30 and prior
versions (the two codepaths appear to me to be unchanged since Jan
2014).
I have made what I think is a fix on trunk, but given it's not a new
issue I'm not sure
Tim noticed an issue with the while working on some changes to ActiveMQ:
https://issues.apache.org/jira/browse/QPID-6447
On 12 March 2015 at 12:52, Justin Ross wrote:
> Hi, everyone. Important defects were discovered soon after I published the
> initial RC. Here is RC 2 from revision 1666029.
>
Thx for the inspiration. I think I will go for (2). This can be easily
extended to cover
situations where the process hosting the sender and the alternate sender
died
by running a simple alternate sender process on the same box.
Thanks
Jan
--
View this message in context:
http://qpid.2158936.
Hi, everyone. Important defects were discovered soon after I published the
initial RC. Here is RC 2 from revision 1666029.
Release artifacts: https://dist.apache.org/repos/dist/dev/qpid/0.32-rc2/
Maven staging repo:
https://repository.apache.org/content/repositories/orgapacheqpid-1028
This
On 03/12/2015 11:16 AM, jml wrote:
one (but important) detail I missed to mention in the simple setup. It
is a one-to-many setup. A number of receivers consuming from the exchange.
As far as I understood a queue is for one-to-one communication.
I need to "broadcast" from a sender to multiple cli
Hi Gordon,
one (but important) detail I missed to mention in the simple setup. It
is a one-to-many setup. A number of receivers consuming from the exchange.
As far as I understood a queue is for one-to-one communication.
I need to "broadcast" from a sender to multiple clients (receivers) and ne
Hi list,
We (FourC) need gentoo ebuilds for qpid components but I've been unable to
find existing complete/maintained packages. The packages I could find are:
https://bugs.gentoo.org/show_bug.cgi?id=389027 - reported problems and not
updated since qpid-cpp-0.14 in 2012.
https://github.com/armills
On 03/11/2015 11:10 AM, jml wrote:
Hi,
consider the following simple setup:
A topic exchange sender in c#, a c++ broker and a topic receiver in c#.
sender created with:
Sender _sender = session.CreateSender("test/AAA.B;{create:always, delete:
always, node:{type:topic}}");
receiver created with
Not sure if this will turn out to be helpful or spam but I've previously
encountered this error message and added the following to our kb:
This is related to an invalid SSL certificate and has been observed in a
situation where the address used to contact the server did not match that
of its certi
Hi Robbie,
I played with it a bit ... what I noticed is that it looks like it
completely ignores the truststore which I pass to the client using the
transport.trustStoreLocation option. Can it be that the
org.apache.qpid.jms.transports.TransportSupport has a bug in the
loadTrustManagers
method? I
We have an error report from a user of the Java broker here:
https://issues.apache.org/jira/browse/QPID-6439
The fix will be trivial, but since it will mean anyone upgrading from
0.30 or earlier to 0.32 will not be able to start their broker after
upgrading, I'd like to get a fix in for this.
--
15 matches
Mail list logo