+1 ... I used the staged artifacts and run them against different versions
of the C++ broker - all seemed to be fine and working.
On Fri, Dec 6, 2019 at 6:39 PM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.48.0 Qpid JMS client release,
> please give it a test out and
+1 ... I used the staged JARs and run tests against different versions of
the C++ broker and all seems fine.
On Fri, Nov 1, 2019 at 8:41 PM Gordon Sim wrote:
> On 01/11/2019 12:37 pm, Robbie Gemmell wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.47.0 Qpid JMS client release,
> >
+1 ... I used the staged JARs and run tests against different versions of
Qpid C++ broker
Jakub
On Tue, Sep 24, 2019 at 11:00 PM Timothy Bish wrote:
> On 9/24/19 1:47 PM, Robbie Gemmell wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.46.0 Qpid JMS client release,
> > please give
Welcome Ben ...
On Mon, Sep 23, 2019 at 11:59 AM Robbie Gemmell
wrote:
> The Qpid PMC have voted to grant commit rights to Ben Hardesty in
> recognition of continued contributions to the project.
>
> Welcome, Ben!
>
> -
> To uns
+1 ... I run tests using the staged JARs against different versions of
Qpidd and all seems to work well.
On Thu, Aug 22, 2019 at 10:56 AM Oleksandr Rudyy wrote:
> +1
>
> * Built from source bundle and ran all tests
> * Verified signatures and checksums
> * Ran successfully Qpid Broker-J integrat
+1 ... used the staging repo and run the client against C++ broker.
On Tue, May 14, 2019 at 3:21 PM Oleksandr Rudyy wrote:
> Hi,
> I built a candidate release for version 6.3.4 of Qpid JMS for AMQP 0-x.
> The release makes legacy JMS client compatible with java 11. It also
> incorporate a number
+1. I used the staged jars and run the client against different versions of
the C++ broker.
On Thu, May 9, 2019 at 4:59 AM Keith W wrote:
> +1
>
> * Verified signatures and checksums
> * Checked for LICENCE and NOTICE files in the archives.
> * ran apache rat-check
> * built from source distrib
+1. I used the staging repo and run the client against different versions
of the C++ broker.
On Wed, Apr 3, 2019 at 9:21 PM Timothy Bish wrote:
> On 4/3/19 1:17 PM, Robbie Gemmell wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.41.0 Qpid JMS client release,
> > please give it a t
Welcome, Jiri, Great to have you here.
On Fri, Mar 1, 2019 at 11:12 AM Robbie Gemmell
wrote:
> The Qpid PMC have voted to grant commit rights to Jiri Danek in
> recognition of continued contributions to the project.
>
> Welcome, Jiri!
>
> Robbie
>
> --
+1 ... I run the client against different versions of the C++ broker and
all seems to be ok. (I used the staging repository)
On Mon, Dec 17, 2018 at 12:47 PM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.40.0 Qpid JMS client release,
> please give it a test out and vot
+1 ... I used the staging repo and run the client against different
versions of the C++ broker.
On Wed, Nov 28, 2018 at 2:37 PM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.39.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source
Congrats and welcome to the community ... and thanks for all your
contributions Roddie!
Jakub
On Tue, Nov 27, 2018 at 3:38 PM Robbie Gemmell
wrote:
> The Qpid PMC have voted to grant commit rights to Roddie Kieley in
> recognition of continued contributions to the project.
>
> Welcome, Roddie!
+1 ... I used the staging repo and run the client against Qpid C++ broker.
On Mon, Nov 12, 2018 at 7:43 PM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.38.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives c
+1 ... built from source on CentOS7 and checked against AQM 1.0 clients.
On Thu, Oct 25, 2018 at 4:00 PM Ganesh Murthy wrote:
> Hello All,
>
> Please cast your vote on this thread to release RC3 as the
> official Qpid Dispatch Router version 1.4.1.
>
> RC3 of Qpid Dispatch Router versi
+1 ... I have built it from source on CentOS and run tests with different
clients against it.
On Mon, Oct 22, 2018 at 2:47 PM Justin Ross wrote:
> Hi, everyone. Please test this release candidate and vote based on what
> you find.
>
> Source archive and signatures:
> https://dist.apache.org/rep
+1 ... I used the staging repository and run my tests against the C++
broker. All seems to work fine.
On Sun, Sep 30, 2018 at 11:21 PM Oleksandr Rudyy wrote:
> +1
>
> * Verified signatures and checksums
> * Built and ran tests from source bundle
> * Ran Qpid Broker-J integration tests on master
+1 ... I used the staging repo and tried it against Qpid C++ broker. All
seems to work fine.
On Thu, Aug 16, 2018 at 1:13 PM Oleksandr Rudyy wrote:
> +1
>
> I performed the following tests:
> * verified checksums and signatures
> * built and ran tests from source bundle
> * ran Qpid Broker-J int
+1 ... I used the staged artifacts with AMQP 0-10 and run some of my tests
against Qpid C++ broker.
On Mon, Aug 13, 2018 at 7:22 PM Oleksandr Rudyy wrote:
> Hi,
>
> I built a candidate release for version 6.3.3 of Qpid JMS AMQP 0-x.
> Please test and vote accordingly.
>
> The source and binary b
+1 ... Used the staged JARs against different versions of Qpid C++ broker.
All seems to work fine.
On Fri, Jul 20, 2018 at 12:10 PM Robbie Gemmell
wrote:
> I have put together a spin for a 0.35.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary
+1 ... build from source on CentOS 7 and used with different clients.
On Mon, Jul 2, 2018 at 6:19 PM Robbie Gemmell
wrote:
> +1
>
> I checked things out as follows:
> - Verified the signature and checksum files.
> - Checked for LICENCE+NOTICE files in the archive.
> - Ran mvn apache-rat:check
+1 ... I used the staging repo and run the client against different
versions of Qpid C++ broker. All seems to work fine.
On Mon, Jun 11, 2018 at 7:32 PM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.33.0 Qpid JMS client release,
> please give it a test out and vote acc
+1 ... build from source on CentOS7 and used with different AMQP 1.0
clients.
On Thu, Jun 7, 2018 at 11:02 PM Ganesh Murthy wrote:
> Hello All,
>
> Please cast your vote on this thread to release RC6 as the
> official Qpid Dispatch Router version 1.1.0.
>
> RC6 of Qpid Dispatch Router
Sounds reasonable to me. The linearstore is around long enough and works
well.
Jakub
On Wed, Jun 6, 2018 at 4:21 PM Kim van der Riet
wrote:
> I would like to propose that the qpid legacystore be deprecated. It has
> been replaced by the linearstore, which is built by default. This has
> been th
+1 ... I build it from source on CentOS7 and used with different AMQP 1.0
clients.
On Fri, May 25, 2018 at 11:45 PM Ganesh Murthy wrote:
> Hello All,
>
> Please cast your vote on this thread to release RC4 as the
> official Qpid Dispatch Router version 1.1.0.
>
> RC4 of Qpid Dispatch R
+1 ... I used the staging repo and run my tests against different versions
of C++ broker with AMQP 0-10. All seems to work for me.
On Wed, May 16, 2018 at 5:44 PM Timothy Bish wrote:
> On 05/15/2018 07:36 AM, Oleksandr Rudyy wrote:
> > Hi folks,
> >
> > I built a candidate release for version 6.
Ups ... I run my tests but forgot the vote :-).
+1 ... I build it from source on CentOS 7 and used with different AMQP 1.0
clients.
On Mon, May 7, 2018 at 7:28 PM, Ganesh Murthy wrote:
> The vote is being extended for a couple more days to give time for people
> to test. Thanks.
>
> On Tue, May
+1 ... I used the staging repo and run the new version against different
versions of the C++ broker. All seems to work fine.
On Mon, Apr 30, 2018 at 5:19 PM, Timothy Bish wrote:
> On 04/30/2018 09:12 AM, Robbie Gemmell wrote:
>
>> Hi folks,
>>
>> I have put together a spin for a 0.32.0 Qpid JMS
+1 ... I build it from source on CentOS 7 and checked it against different
clients.
On Fri, Mar 23, 2018 at 3:40 PM, Timothy Bish wrote:
> +1
>
> * Validated signatures and checksums
> * Built from source and ran the tests
>
>
> On 03/23/2018 08:45 AM, Robbie Gemmell wrote:
>
>> On 22 March 2018
+1 ... I used the staging repo and run my tests against different versions
of the C++ broker.
On Sat, Mar 24, 2018 at 9:39 AM, Keith W wrote:
> +1
>
> * Validated signatures and checksums
> * ran apache rat-check
> * built from source distribution artefact and ran all tests (mvn
> verify with Ja
+1. I have build it from source and used it with C++ broker and different
clients.
On Sun, Mar 4, 2018 at 4:37 AM, Roddie Kieley wrote:
> +1 (advisory)
>
> - checked out the tag 0.21.0-rc1
> - Built on OSX 10.11.6 w/Xcode 7.3.1 command line tools without ruby or
> valgrind
> -- Tested with go-te
+1 ... I used the staging repo and run tests against different versions of
the C++ broker (including master)
On Mon, Feb 26, 2018 at 1:18 PM, Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.30.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
+1 ... I built it from source on CentOS 7 and run it against different AMQP
clients.
On Tue, Feb 20, 2018 at 9:27 PM, Ted Ross wrote:
> Please vote on this thread to release qpid-dispatch 1.0.1-rc1 as the
> official 1.0.1.
>
> The release can be found here:
>
> https://dist.apache.org/repos/
+1 ... I build it from source and used it with C++ broker and Dispatch.
On Sun, Jan 28, 2018 at 11:36 PM, Keith Wall wrote:
> +1
>
> 1) Built from source bundle and ran unit tests on Ubuntu 16.04.3 (VM)
> 2) Executed cpp command line examples against Broker-J (master)
>
>
> On 26 January 2018 at
Hi Jan,
This is an example which I found in my notes:
call 120 queueMoveMessages SrcQueue DstQueue 10
{"filter_type":"header_match_str","filter_params":{"header_key":"qpid.subject","header_value":"key1"}}
I haven't used it for some time, but give it a try, I think it should still
work.
Thanks &
+1 ... I used the staging repo and run my tests against different versions
of C++ broker.
On Fri, Jan 19, 2018 at 1:30 PM, Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.29.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and b
Hi Jan,
The QMF GUI source code can be found here:
https://github.com/apache/qpid/tree/trunk/qpid/tools/src/java
I think it should still work, but I think it wasn't touched for quite a
long time.
Regards
Jakub
On Thu, Jan 18, 2018 at 11:27 AM, Jan Bares, WOOD & Co.
wrote:
> Hi,
>
> There used
id::messaging API ? Everything that can be done with qpid-config
> can be done also with the API ?
>
> Best regards,
> Daniel
>
>
> > On 13.01.2018, at 17:23, Jakub Scholz wrote:
> >
> > The LVQ queue is able to persist these messages to disk like any other
&
The LVQ queue is able to persist these messages to disk like any other
queue. So they can survive restart.
Jakub
On Sat, Jan 13, 2018 at 4:55 PM, Daniel Gavrila
wrote:
> Hello Andreas,
>
> Thanks for the suggestion.From what I read from documentation, indeed a
> last value queue should cover a
+1 ... I used the staging repo and run my tests against different version
of the C++ broker (including master).
On Mon, Dec 11, 2017 at 8:30 PM, Robbie Gemmell
wrote:
> On 11 December 2017 at 18:21, Robbie Gemmell
> wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.28.0 Qpid JMS c
+1 ... I run my tests against different versions of Qpid C++ broker
On Wed, Nov 22, 2017 at 9:10 PM, Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a Qpid Python 1.37.0 release, please
> give it a test out and vote accordingly.
>
> The source archive can be grabbed from:
>
nd. I would like senders to be anonymous.
> The idea is to communicate via an exchange but it should not be possible -
> even with a network sniffer - to identify the sender.
>
> Kind Regards
> Andreas
>
>
>
> On Tue, Nov 21, 2017 at 6:23 PM, Jakub Scholz wrote:
>
> >
+1 ... I built it from source and run different AMQP 0-10 and 1.0 clients
against the broker. All seems to work fine.
On Tue, Nov 21, 2017 at 10:51 PM, Timothy Bish wrote:
> On 11/21/2017 01:20 PM, Robbie Gemmell wrote:
>
>> Hi folks,
>>
>> I have put together a spin for a Qpid CPP 1.37.0 releas
AFAIK the AMQP message has a property called user-id. This can be set by
the client and the broker would verify that if it is set it contains the
user-id of the connected user and not some other user-id. So you can use it
to identify the sender. However, some clients simply leave it empty (and
some
+1 ... I built it from source and run some of my tests with different AMQP
1.0 clients as well as against the Qpid C++ broker.
Jakub
On Tue, Nov 14, 2017 at 2:01 PM, Ted Ross wrote:
> Please cast your vote on this thread to release RC3 as the official Qpid
> Dispatch Router version 1.0.0.
>
> Q
+1 ... I used the staging repo and run my tests against different versions
of Qpid C++ broker.
Jakub
On Wed, Nov 15, 2017 at 4:59 PM, Oleksandr Rudyy wrote:
> Hi all,
>
> I built a candidate release for version 6.3.0 of Qpid JMS AMQP 0-x.
>
> Please test and vote accordingly.
>
> The source and
Hi Andreas,
The problem is that in qpidd you never publish directly to queue or read
directly from an exchange. You always publish to exchange and read from a
queue. In reality what you see as publishing directly to an queue is
sending the message to an exchange named "" (as in empty string) with
+1 ... I used the staging repo and run my tests against different versions
of Qpid C++ broker.
On Wed, Nov 1, 2017 at 6:56 PM, Robbie Gemmell
wrote:
> On 1 November 2017 at 16:37, Robbie Gemmell
> wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.27.0 Qpid JMS client release, plea
+1. I build it from source code and used it with Qpid C++ broker (master)
and Qpid Dispatch (1.0.0 RC1) and run my tests against them. All seems to
work fine.
On Wed, Oct 18, 2017 at 7:29 PM, Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a first spin for a Qpid Proton 0.18.0 release,
+1. I used the staged jars and run them against different versions of the
C++ broker (master, 1.36, 1.35 and 0.34). All looks OK.
On Wed, Oct 4, 2017 at 10:12 PM, Gordon Sim wrote:
> On 04/10/17 12:35, Robbie Gemmell wrote:
>
>> I have put together a spin for a 0.26.0 Qpid JMS client release, pl
+1 ... used the staged artifacts and run my tests against different
versions of Qpid C++ broker (including the latest master).
On Mon, Sep 18, 2017 at 9:02 PM, Timothy Bish wrote:
> On 09/18/2017 12:45 PM, Robbie Gemmell wrote:
>
>> Hi folks,
>>
>> I have put together a spin for a 0.25.0 Qpid JM
std::string& type = "");
>
> to provide the name and options. It seems the behaviour is not the same
> though as your method also works for me. Problem solved, thanks very much
> :)
>
> C
>
> On 26 August 2017 at 14:30, Jakub Scholz wrote:
>
> > How exac
How exactly do you create the address and what do you have in you client /
broker log?
When I try to do something like this:
Address myAddress;
Variant::Map options;
Variant::Map selector;
selector["selector"] = "color='blue'";
options["link"] = selector;
Variant::Map node_
Perhaps a stupid question ... but have you tried installing the
liblinearstore (liblinearstore_1.36.0-1qpid+xenial1_amd64.deb) package?
According to the changelog it has been renamed from qpidd-linear-store.
Jakub
On Wed, Aug 23, 2017 at 3:34 PM, Morgan Lindqvist <
morgan.lindqv...@ericsson.com>
ut I'm not sure
they ever did - at least I cannot find anything. I'm not sure why I didn't
raised a QPID JIRA for it my self. :-(
I probably haven't tried it since 2015. So if it works for Gordon it might
be already fixed in master.
Regards
Jakub
On Mon, Aug 21, 2017 at 11:
This is definitely not new in 1.36. I think this is present "since the
beginning". :-(
If I remember correctly the problem was that the NSS library which handles
the SSL certificates is initialised only once even when you create multiple
connections. I was quite sure this was already discussed in
Welcome Adel. Great to have you here!
On Thu, Aug 10, 2017 at 11:31 AM, Oleksandr Rudyy wrote:
> Welcome Adel!
>
> On 9 August 2017 at 11:49, Robbie Gemmell
> wrote:
>
> > The Qpid PMC have voted to grant commit rights to Adel Boutros in
> > recognition of continued contributions to the project
+1. I used the staging repo and run the JMS client against different
versions of the Qpid C++ broker.
J.
On Fri, Aug 4, 2017 at 11:42 PM, Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.24.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
>
ad a) This would solve the issue when the "peers only" truststore is used.
The point that without the "peers only" store you can easily circumvent
this is valid, but I don't think that this new feature would make the
situation any worse. Perhaps the code it self can be included directly in
the Peer
I think that if you want the broker to present the whole chain you have to
load the chain into the certutil database. You can download the
intermediate certificate here:
https://letsencrypt.org/certs/lets-encrypt-x3-cross-signed.pem.txt
And simply add it to the certutil database:
certutil -
+1 ... I checked the Java broker and the 0-10 client. I also run the 0-10
client against the C++ broker.
On Fri, Jun 23, 2017 at 5:29 PM, Rob Godfrey
wrote:
> +1
>
> Built from source and ran the system tests
> Started the broker and used the management console.
> Ran some ad hoc tests using the
+1 ... I checked the Java broker and the 0-10 client. I also run the 0-10
client against the C++ broker.
On Fri, Jun 23, 2017 at 10:47 PM, Oleksandr Rudyy wrote:
> +1
>
> * verified checksums and signatures
> * built from sources and ran tests
> * started broker
> * created queue from web manage
This is lot easier in C++ broker where you cannot change the policy or the
limits once you create the queue :-). But as a user I would have
appreciated the possibility to change the limits on the fly many times, so
I'm not suggesting this is the way to go.
>From your possibilities B) would be what
Hi,
Last time I built Qpid Proton on MacOS was about a month ago. I don't
really have a guide for you. But I don't remember doing anything special to
make it work (I was surprised my self that it simply worked). I used
homebrew to install all needed tools and dependencies, but they were not
that m
FYI: I raised it as DISPATCH-779 (
https://issues.apache.org/jira/browse/DISPATCH-779)
Thanks & Regards
Jakub
On Mon, May 22, 2017 at 9:14 PM, Jakub Scholz wrote:
> Hi Ted,
>
> Ok, thanks. I will try to collect some logs and raise a JIRA.
>
> Thanks & Regards
> Jaku
Hi Ted,
Ok, thanks. I will try to collect some logs and raise a JIRA.
Thanks & Regards
Jakub
On Mon, May 22, 2017 at 8:55 PM, Ted Ross wrote:
> Hi Jakub,
>
> I think your expected behavior should be the correct one for multicast.
> This is a bug.
>
> -Ted
>
>
>
Hi,
In Dispatch, I can configure the multicast addresses:
address {
prefix: /someAddress
distribution: multicast
}
My general expectation for such multicast address would be that:
- The credit for sending messages is maintained by the router automatically
independently on any receivers
Could you try to start the broker like this:
qpidd --no-module-dir --load-module amqp.so --load-module
linearstore.so --auth no
Does the warning message still appear?
There used to be the store.so module which wasn't really message store on
its own, but it was used for some SQL based message
+1 ... I used the staging repo and run my tests against different versions
of Qpid C++ broker.
On Fri, May 12, 2017 at 7:07 PM, Robbie Gemmell
wrote:
> On 12 May 2017 at 17:41, Robbie Gemmell wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.23.0 Qpid JMS client release, please
>
The management tools should be now part of the C++ broker source tree:
https://github.com/apache/qpid-cpp/tree/master/management/python ... they
are also in the 1.36.0 release archives (management / python).
Jakub
On Sun, Apr 30, 2017 at 2:41 PM, Fraser Adams wrote:
> Hello All,
>
> qpid-tools
+1 ... I checked the RC against different clients and as well as against
the Qpid C++ broker
On Wed, Apr 26, 2017 at 2:15 PM, Ted Ross wrote:
> Please cast your vote on this thread for releasing RC3 as the official
> 0.8.0.
>
> The following issue has been resolved since RC2:
>
> DISPATCH-74
+1 ... I used the staging repo and run my tests against different versions
of Qpid C++ and MRG-M brokers.
On Mon, Apr 17, 2017 at 7:34 PM, Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a spin for a 0.22.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
>
Hi,
I was playing over the weekend with Proton's binging for Go language (I was
using the Electron API). I works quite nicely, but I didn't managed to get
it connected to my broker using SASL EXTERNAL mechanism. When I configure
EXTERNAL in the AllowedMechs in ConnectionOptions, I always get follo
+1
I built it from the source and ran Dispatch against different clients and
brokers.
On Fri, Apr 7, 2017 at 6:00 PM, Robbie Gemmell
wrote:
> On 7 April 2017 at 15:34, Ted Ross wrote:
> > Please cast your vote on this thread for releasing RC2 as the official
> > 0.8.0.
> >
> > Thanks,
> >
> >
I think that might depend on the OS etc. In my build on CentOS 7 it is in
/usr/lib64/qpid/daemon/ ...
$ ls /usr/lib64/qpid/daemon/
amqp.so linearstore.so xml.so
When the module is loaded, the broker log should print following message
when starting:
2017-03-31 18:23:12 [Broker] info Loaded proto
Hi Mark,
Last time I used the Python binding against the C++ API on Ubuntu (I
actually use it against Qpid C++ broker and not against ActiveMQ, but with
AMQP 1.0) I had following packages installed from ppa:qpid/testing (+ some
SASL libraries for authentication etc.):
- libqpid-proton6
- libqpidcl
+1 ... I run my tests against different versions of Qpid C++ broker
On Fri, Mar 10, 2017 at 8:58 PM, Timothy Bish wrote:
> +1
>
> * Validated the signatures and checksums
> * Checked for license and notice files in the source and binary archives
> * Built from source and ran the tests.
> * Check
, rammohan ganapavarapu <
rammohanga...@gmail.com> wrote:
> Jakub,
>
> in older versions there is a qpid/libexec/resize tool right, do we need and
> or have the similar or same tool in 1.35 version?
>
> Ram
>
> On Mar 9, 2017 3:33 AM, "Jakub Scholz" wrote:
>
>
Hi,
What do you mean with resizing queue store? With linear store, the journal
files should be created "on demand", you don't have to do any resizing. The
only limits for your queue are the size and count limits. There are no
store limits like they used to be with the old legacy store.
Jakub
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 <
morgan.lindqv...@e
Thanks a lot. All seems to work fine now.
Regards
JAkub
On Wed, Feb 15, 2017 at 10:23 PM, Kim van der Riet
wrote:
> Doh!!!
>
> ... and it was on the same line I just fixed :-(
>
> Ok, checked in an additional fix on master.
>
>
> On 02/15/2017 02:33 PM, Jakub S
tatement with a more traditional version
> that should not require c++11. See QPID-7676.
>
> Kim
>
>
> On 02/14/2017 05:18 PM, Jakub Scholz wrote:
>
>> Hi Alan,
>>
>> Thanks for your help. The -std=c++11 flag indeed helps to work around the
>> problem.
&
Hi Alan,
Thanks for your help. The -std=c++11 flag indeed helps to work around the
problem.
Thanks & Regards
Jakub
On Mon, Feb 13, 2017 at 3:42 PM, Alan Conway wrote:
> On Fri, 2017-02-10 at 22:46 +0100, Jakub Scholz wrote:
> > Hi,
> >
> > I seem to be unable to b
Hi,
I seem to be unable to build the latest master of Qpid C++ broker. It seems
to complain about the round function not being in std (the complete output
is below). It seems to be related to QPID-7666 / commit 34cfb7f.
I'm compiling it on CentOS 7 with g++ version 4.8.5, Make version 3.82 and
cm
+1 ... I used the RC1 to build Qpid C++ broker and run my AMQP 1.0 tests
against it. All seems to be OK.
On Fri, Feb 3, 2017 at 6:35 PM, Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a first spin for a 0.17.0 Qpid Proton release,
> please test it and vote accordingly.
>
> Note that P
+1 ... I used the RC1 with Qpid JMS and run my tests against the Qpid C++
broker. All seems to be OK.
On Fri, Feb 3, 2017 at 8:25 PM, Timothy Bish wrote:
> +1
>
> * Review the license and notice files
> * Verified the signatures and checksums
> * Checked using the rat check goal that all files a
I'm afraid that there are no detailed configuration options for TLS/SSL in
the C++ broker. You cannot configure the enabled / disabled cipher suites,
protocols and stuff like that.
J.
On Thu, Feb 2, 2017 at 9:40 PM, wrote:
> Looking for a way to set the SSL/TLS transport options on the broker,
+1 ... I used the staged artefacts and run my tests against the C++ broker.
On Tue, Jan 17, 2017 at 2:20 PM, Robbie Gemmell
wrote:
> On 16 January 2017 at 18:38, Robbie Gemmell
> wrote:
> > Hi folks,
> >
> > I have put together a spin for a 0.20.0 Qpid JMS client release,
> > please test it and
Sounds reasonable to me. I guess that as always ... in case it would be
needed we can have some patch releases for some critical bugs or security
issues.
Jakub
On Mon, Jan 9, 2017 at 11:28 PM, Robbie Gemmell
wrote:
> I'd like to propose dropping support for Java 7 in the broker and both
> JMS
+1 ... I checked the broker and also the 0-10 client. All looks OK.
On Wed, Dec 21, 2016 at 11:56 AM, Keith W wrote:
> +1.
>
> My testing was:
>
> 1) Verified the md5/sha checksums on all distribution artefacts
> 2) Verified signatures on all all distribution artefacts
> 3) Built/ran test profil
You can run "schema" command. It will show you list of all the different
QMF classes. Afterwards you can call "schema " ... e.g. "schema
queue" and it will list details about the class. That includes the
attributes as well as the methods and their arguments. The method has to
correspond to the obje
+1 ... I run tests using different 0-10 and 1.0 clients, all seems to be OK.
On Fri, Dec 9, 2016 at 7:42 PM, Robbie Gemmell
wrote:
> On 9 December 2016 at 18:01, Robbie Gemmell
> wrote:
> > Hi folks,
> >
> > I have put together a first spin for a Qpid CPP 1.36.0 release, please
> > test it and
+1 ... I focused mainly on the broker and the AMQP 0-10 client, which I
tested also against various versions of the Qpid C++ broker.
On Thu, Nov 10, 2016 at 7:13 PM, Oleksandr Rudyy wrote:
> Hi folks,
>
> Qpid for Java 6.1.0 RC2 is available for testing.
>
> The changes against the following JI
+1 ... I have build it from source and run my tests with different clients
and Qpid C++ broker against the RC2.
On Thu, Nov 10, 2016 at 7:26 PM, Ted Ross wrote:
> I have built RC2 for Qpid Dispatch Router 0.7.0. Please give it a test
> and cast your votes.
>
> The build artifacts can found here
Do your connections use heartbeat? The heartbeat will make sure that when
the client doesn't communicate within two heartbeat intervals, the broker
will close the connection. I believe that without the heartbeat, the broker
has to rely on the TCP stack which is not always reliable and might behave
Can you reproduce it?
Maybe you can try to increase the log levels in the broker to get some more
information about why it crashed (
http://qpid.apache.org/releases/qpid-cpp-1.35.0/cpp-broker/book/ch01.html#RASC-logging-options).
If the broker crashed, you can also try to get a core dump for furth
Hi Ram,
This should normally not crash the broker. This error should be only sent
to the client which exceeded the max queue size limit and that particular
client might be kicked out. But the broker should continue running and
serving other clients. Why do you think the broker crashed because of t
ome times it times out, i hope we new version will have faster
> recovery mechanism.
>
> Ram
>
> On Fri, Oct 21, 2016 at 11:12 AM, Jakub Scholz wrote:
>
> > These are two separate things.
> >
> > The linearstore is the persistent message store. When you crea
up002-consumer-group-001-dl --durable --file-size=6000
> --file-count=4 --max-queue-size=52428800 --max-queue-count=10
> --limit-policy=flow-to-disk --argument no-local=False
>
> One more question, is background recovery feature available in cpp broker
> as well like
ect - Reject enqueued messages
> flow-to-disk - Page messages to disk
> ring - Replace oldest
> unacquired message with new
> ring-strict- Replace oldest message,
> reject
ating queues? if i dont create queues with "paging"
> options what is behavior of broker?
>
> Thanks,
> Ram
>
> On Thu, Oct 20, 2016 at 3:20 PM, Jakub Scholz wrote:
>
> > Hi,
> >
> > Do you have the module installed in the path you mentioned? If yes, the
1 - 100 of 396 matches
Mail list logo
