Re: [Dispatcher] system_tests_protocol_family test fails if no ipv6 is supported

quot;. This is > because tests/policy-1/policy-safari.json and > tests/policy-1/policy-boardwalk.json have has "::1" in the localhost field. > I can't find a way to tell the test to ignore this value if the machine is in > ipv4 mode and to keep it in case we have both... > > An

Re: [Qpid-dispatch] Duplication between sslProfile and connector options

Hi Adel, Can you please setup your listener like this - listener { host: 0.0.0.0 port: 10399 saslMechanisms: ANONYMOUS sslProfile: ssl-profile-name authenticatePeer: no# Use authenticatePeer instead of requirePeerAuth requireSsl: yes } Thanks. -

Re: [Qpid-dispatch] Duplication between sslProfile and connector options

Hi Adel, Going forward please use the camelCase and abandon using dashed properties (like cert-file). Following is an example of the *correct* way to use certFile sslProfile { certFile: /home/gmurthy/opensource/server-certificate.pem keyFile:

Re: [Qpid-dispatch] Duplication between sslProfile and connector options

Hi Adel, You can find the entire list of entities and attributes here - http://qpid.apache.org/releases/qpid-dispatch-master/man/qdrouterd.conf.html I will purge the book of dashed entity/attribute names on the master branch. I have entered a JIRA for this so it can be tracked -

Re: Qdstat, SASL and user with @domain

- Original Message - > From: "Gordon Sim" <g...@redhat.com> > To: users@qpid.apache.org > Sent: Wednesday, June 1, 2016 12:10:23 PM > Subject: Re: Qdstat, SASL and user with @domain > > On 01/06/16 17:05, Ganesh Murthy wrote: > >

Re: [qpid-dispatch] Crash when trying to close a NULL listener

Hi Adel, Can you please list the steps that caused this crash to occur? Would be great if you could send a reproducer. Thanks. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Tuesday, May 31, 2016 9:38:42 AM > Subject:

Re: [Qpid-dispatch] Duplication between sslProfile and connector options

- Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Tuesday, June 21, 2016 5:33:36 AM > Subject: RE: [Qpid-dispatch] Duplication between sslProfile and connector > options > > Thank you Ganesh, > > I actually got it working using

Re: [Qpid-Dispatch] SSL/SASL configuration on a listener

these self signed certs and also cover various SASL scenarios. Thanks. - Original Message - > From: "Ganesh Murthy" <gmur...@redhat.com> > To: users@qpid.apache.org > Sent: Thursday, June 23, 2016 10:05:08 AM > Subject: Re: [Qpid-Dispatch] SSL/SASL configu

Re: [Qpid-Dispatch] SSL/SASL configuration on a listener

Hi Adel, When creating self signed certificates, it is always a good idea to create a root CA and use it to sign the server and client certificates. If you are creating self signed certs in a production environment, I would suggest that you create a root CA and use the root CA to create an

Re: [Qpid-dispatch] Duplication between sslProfile and connector options

Hi Adel, It was not clear from your email if you got SSL working on your dispatch router. Here are the steps I used to create the ca certs/server certs using openssl and use them in the dispatch router - # Create the root CA private key for the CA cert, this key is password protected

Re: [Qpid-Dispatch] SSL/SASL configuration on a listener

> Thanks. > > - Original Message - > > From: "Ganesh Murthy" <gmur...@redhat.com> > > To: users@qpid.apache.org > > Sent: Thursday, June 23, 2016 10:05:08 AM > > Subject: Re: [Qpid-Dispatch] SSL/SASL configuration on a listener > > > > H

Re: [Qpid-Dispatch] SSL/SASL configuration on a listener

spatch/etc/ssl-my-certs/root/ca1/client-private-key.pem > > > --ssl-password=client-password > > > Connections > > > Id host container > > > roledir security > > > authentication > > > > > >

Re: [Qpid-Dispatch] SSL/SASL configuration on a listener

t; > > > > > > > > > > > > > > > ssl-profile { > > > > > > certFile: > > > > > > > > > > > > /home/gmurthy/opensource/dispatch/etc/ssl-my-certs/root/ca1/server-certificate.pem > > > > > > keyFile: > > > > &

Re: [Qpid-Dispatch] SSL/SASL configuration on a listener

t; > > == > > > > > > > > > > > > > > > Dispatcher conf > > > > > > > > > > > > > > > == > > > > > > > > > > > > > > > container { > > > > > > > > > > > > > >

Re: Dispatch router load balancing with java clients

Hi Noel, Looking at your java producer code, I suspect that the messages are sent synchronously (even though jms.forceAsyncSend=true). Every message sent is synchronous meaning that the sender expects an acknowledgment before sending the next message. This means that only one message is in

Re: [VOTE] Release RC 3 as Qpid Proton 0.12.0

can vote. When we tally up the results, we separate the binding (committer) from the non-binding votes, but we use all the votes in our decision nonetheless. On Wed, Feb 10, 2016 at 7:11 AM, Ganesh Murthy <gmur...@redhat.com> wrote: > I cannot vote but I did the following on Fedo

Re: [VOTE] Release RC 3 as Qpid Proton 0.12.0

I cannot vote but I did the following on Fedora 22 - 1. Downloaded and compiled the proton 0.12.0 RC3 source and ran all unit tests (including the ones I added) successfully 2. Made dispatch router master use Qpid Proton 0.12.0 RC 3. Ran dispatch unit tests successfully. 3. Made sure that the

Re: Hekp with Dispatch Build "difficulties"

Hi Paul, I tried to get a Docker environment going with CentOS 5 but ran into several problems. CentOS 5 is pre-2008 and has an old version of Python. Is there a way you can get to a recent version of CentOS (CentOS 7?). If you want to stay on CentOS 5, please try using dispatch 0.4 and

Request to include fix for PROTON-1088 in Qpid-Proton release 0.12.0

Hello All, I have a fix for https://issues.apache.org/jira/browse/PROTON-1088 and this fix needs to be in Proton 0.12.0 but did not make it to the alpha release Here are the commits (2 commits because I forgot to include the SSL stubs in the first commit) (thanks kgiusti and astitcher) (1)

Re: Qpid Dispatch Router log configuration

Thanks Ulf. This is fixed now. http://qpid.apache.org/releases/qpid-dispatch-master/man/qdrouterd.conf.html#log - Original Message - > From: "Ted Ross" > To: users@qpid.apache.org > Sent: Wednesday, May 11, 2016 8:51:41 AM > Subject: Re: Qpid Dispatch Router log

Re: [qpid-dispatch] Running same qdmanage command twice crashes dispatcher

Hi Adel, I got down the latest dispatch code from https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.6.0-beta2/ and used your dispatcher.conf to start the router. I ran the qdmanage command several times and did not see the router crash. This is what I see on the client side -

Re: [Qpid-dispatch] Typo in the manual page of qdmanage

Hi Adel, The rest of the default value is now showing up - Connection Options. -b URL, –bus=URL : URL of the messaging bus to connect to (default 0.0.0.0) Please see - http://qpid.apache.org/releases/qpid-dispatch-master/man/qdmanage.html Thanks Alan Conway for fixing this. Thanks. -

Re: [qpid-dispatch 0.6.0] Unable to set "sslProfileName" when creating a connector using qdmanage

Hi Adel, I have entered a JIRA - https://issues.apache.org/jira/browse/DISPATCH-446 to make sslProfile an entity instead of an annotation. After completion of this JIRA, you should be able to use the sslProfile in the connector like Ted suggested. Thanks. - Original Message - >

Re: [VOTE] Release Qpid Dispatch Router 0.6.1

+1 * Downloaded distribution * Verified checksums * Verified that patch to DISPATCH-367 and relevant units tests are present. * Ran all unit tests successfully Thanks. - Original Message - > From: "Ken Giusti" > To: users@qpid.apache.org > Sent: Wednesday, August

Re: qpid-dispatch link between brokers

Please take a look at the autoLink feature provided by the router (http://qpid.apache.org/releases/qpid-dispatch-master/book.html - section 2.5). You can create an "address" with prefix jms.queue and then setup two autoLinks in and out of the brokers. Create queues (jms.queue.first) in the

Re: [qpid-dispatch 0.6.0] Unable to set "sslProfileName" when creating a connector using qdmanage

- Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Wednesday, July 13, 2016 9:46:36 AM > Subject: RE: [qpid-dispatch 0.6.0] Unable to set "sslProfileName" when > creating a connector using qdmanage > > Hello Ganesh, > > Can you

Re: [qpid-dispatch 0.6.0] Unable to set "sslProfileName" when creating a connector using qdmanage

Take a look at at https://github.com/apache/qpid-dispatch/blob/master/python/qpid_dispatch/management/qdrouter.json. It says - "sslProfileName": { "type": "string", "description": "The name of the ssl profile. This is for internal use only. Use the 'name' attribute to assign a name

Re: [qpid-dispatch] Typos in the manual page of qdmanage

This commit on the master branch took care of it - https://github.com/apache/qpid-dispatch/commit/c0be15664e24625d59cab5fdb9219fc9e997558e http://qpid.apache.org/releases/qpid-dispatch-master/qdmanage.8.html should look good. Thanks. - Original Message - > From: "Adel Boutros"

Re: [Qpid-Dispatch] SSL/SASL configuration on a listener

; > > > > > > host: 0.0.0.0 > > > > > > > > > > > > > port: 10398 > > > > > > > > > > > > > saslMechanisms: EXTERNAL > > > > > > > > > > > > > sslProfile: my-ssl-profile > > > >

Re: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

- Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Friday, July 1, 2016 9:00:53 AM > Subject: [Qpid-Dispatch] qdmanage query doesn't take into account the name > option when passed > > Hello, > > Using qpid-dispatch 0.6.0, I have

Re: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

Link to the Management spec draft - https://www.oasis-open.org/committees/download.php/54441/AMQP%20Management%20v1.0%20WD09 - Original Message - > From: "Ganesh Murthy" <gmur...@redhat.com> > To: users@qpid.apache.org > Sent: Friday, July 1, 2016 10:26:4

Re: [Qpid-Dispatch] Dynamic port allocation from the command line

Please add a JIRA for this. Thanks. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Wednesday, June 29, 2016 6:42:02 AM > Subject: [Qpid-Dispatch] Dynamic port allocation from the command line > > Hello, > > In Qpid Java Broker, we

Re: [Dispatch router 0.7.0] [Proton 0.16.0] SSL commands failing on the Dispatch Router on Linux

Hi Adel, Why is your router mode set to 'interior'? Do you have more than one router involved? If not, the mode should be set to 'standalone'. Thanks. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Wednesday, February 1, 2017

Re: [Dispatcher] system_tests_protocol_family test fails if no ipv6 is supported

all references to IPv6 in the tests. > > > Have you found a better alternative? It seems that Chuck suggested it could > be done using C code. > > > Regards, > > Adel > > > From: Ganesh Murthy <gmur...@redhat.co

Re: [GitHub] qpid-dispatch pull request #140: DISPATCH-216 - Added code to skip system_te...

skipped 'Skipping test..IPV6 not enabled' > 19: > 19: -- > 19: Ran 1 test in 0.001s > 19: > 19: OK (skipped=1) > 1/1 Test #19: system_tests_protocol_family . Passed0.11 sec > > Regards, > Adel

Re: [GitHub] qpid-dispatch pull request #140: DISPATCH-216 - Added code to skip system_te...

ing shown. > I am also attaching the patch which I had used to disable IPv6 brutally (Of > course it is not a patch to be accepted but just to show you what we had to > do to ignore the errors). > Regards, > Adel > From: Ganesh Murthy <gmur...@redhat.com> > Sent: Tuesday,

Fwd: [GitHub] qpid-dispatch pull request #140: DISPATCH-216 - Added code to skip system_te...

close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #140 commit a0b16449e7fd257b2abee347ae211ab6a33bc53c Author: Ganesh Murthy <gmur...@redhat.com> Date: 2017-01-31T19:18:10Z DISPATCH-21

Re: [Dispatch router 0.7.0] [Proton 0.16.0] SSL commands failing on the Dispatch Router on Linux

> > Hello Ganesh, > > We are not in the stage of deploying multiple dispatch routers yet. > > However may I know why you think this is the cause of the below failure? > > Regards, > Adel > > Get Outlook for Android<https://aka.ms/ghei36> > >

Re: [VOTE] Release Qpid Proton 0.17.0

ree its not great. > > I was under the impression those bits were being built in CI, but this > suggests otherwise, so if not and they also arent working we probably > need to have a discussion around what to do with them (in its own > thread). > > Robbie > > On 3 Feb

Re: Dispatch Router console output

When you start the dispatch router, it puts out a line on the console saying something like this - "Thu Jan 26 14:46:53 2017 SERVER (info) Running in DEBUG Mode" That means that the router is ready to receive requests. If you want to see all all detailed trace messages from all router modules

Re: [Dispatcher] system_tests_protocol_family test fails if no ipv6 is supported

rry, I have not found a better alternative. I would love to hear from you if you can submit a patch in C. Thanks. > > Regards, > > Adel > > > From: Ganesh Murthy <gmur...@redhat.com> > Sent: Monday, June 6, 2016 11:33:05 PM &

Re: [Dispatch Router] Unexpected behavior when starting the same dispatch router twice

0.8 is expected to come out around mid February. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Friday, January 20, 2017 8:31:40 AM > Subject: Re: [Dispatch Router] Unexpected behavior when starting the same > dispatch router twice

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

- Original Message - > From: "Robbie Gemmell" > To: users@qpid.apache.org > Sent: Friday, January 20, 2017 2:18:45 PM > Subject: Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms > > On 20 January 2017 at 19:06, Gordon Sim wrote: > >

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

gt;>> capabilities=null}, target=Target{address='null', durable=NONE, > > >> >>>> expiryPolicy=LINK_DETACH, timeout=0, dynamic=true, > > >> >>>> dynamicNodeProperties={lifetime-policy=DeleteOnClose{}}, > > >> >>>

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

t; >> >>>> linkCredit=250, available=null, drain=false, echo=false, > >> properties=null} > >> >>>> [1244186219:1] -> Attach{name='qpid-jms:receiver > >> >>>> :ID:53f2be62-ad72-4193-a824-3293ffc5

Re: [Dispatch Router] Dispatch router not able to use Proton 0.16.0

Hi Adel, This problem has been fixed on the master branch via https://issues.apache.org/jira/browse/DISPATCH-569 It will be available in the 0.8.0 release of the Dispatch Router. Thanks. - Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org

Re: Patch + jira vs pull request

A few days back, I had emailed Travis support and asked them why the builds were taking too long to start. This is what they said - "I've been taking a look at the logs and it appears that at the time when your build #199359621 was triggered, the Apache organization was running at capacity,

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

Hi Adel, We did notice the same problem you are seeing and we did end up increasing the timeout from 5 to 10 (although on a different test) as seen in this commit on master branch - https://github.com/apache/qpid-dispatch/commit/5e6b2e65b2ea9614d7619711961d38aceefb49d4 Is it correct that

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

iving 8 messages out of 10. I didn't > check it on the trunk however to see if it is fixed. > > > Regards, > > Adel > > > From: Ganesh Murthy <gmur...@redhat.com> > Sent: Tuesday, February 28, 2017 3:58:37 PM > To: users@qpid.apache.org &

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

ll}, target=Target{address='$management', > >> >> durable=NONE, > >> >> >>>> expiryPolicy=SESSION_END, timeout=0, dynamic=false, > >> >> >>>> dynamicNodeProperties=null, capabilities=[queue]}, unsettled=nu

Re: dispatch router configuration

Hi Vince, The role of "on-demand" for a connector has been deprecated. I think you are seeing a segfault because your config does not seem to have a "router" section defined which should look something like the following - router { mode: standalone id: Router.A } Can you please add

Re: [VOTE] Release Qpid Dispatch Router 0.7.0 (RC2)

+1 Verified file checksum Compiled from source using Proton 0.13 Passed all unit tests Verified that fixes for DISPATCH-535 and DISPATCH-533 are present and tested them Verified simple_send.py and simple_recv.py work Thanks - Original Message - > From: "Chuck Rolke"

Re: Qpid Proton/Dispath trace : correlate connection identifier and remote IP/port

- Original Message - > From: "Robbie Gemmell" > To: users@qpid.apache.org > Sent: Wednesday, November 23, 2016 7:58:48 AM > Subject: Re: Qpid Proton/Dispath trace : correlate connection identifier and > remote IP/port > > On 23 November 2016 at 08:04, Paolo

Re: Qpid Proton/Dispath trace : correlate connection identifier and remote IP/port

xperience<http://paolopatierno.wordpress.com/> > > > > From: Ted Ross <tr...@redhat.com> > Sent: Wednesday, November 23, 2016 2:56 PM > To: users@qpid.apache.org > Subject: Re: Qpid Proton/Dispath trace : correlate connection identi

Re: [VOTE] Release Qpid Dispatch Router 0.7.0 (RC1)

-1 kgiusti ran a coverity scan on RC1 which found 7 memory leaks. These need to be fixed. I have entered a JIRA with the details - https://issues.apache.org/jira/browse/DISPATCH-526 Thanks. - Original Message - > From: "Ted Ross" > To: users@qpid.apache.org >

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

- Original Message - > From: "Adel Boutros" > To: users@qpid.apache.org > Sent: Thursday, March 30, 2017 9:04:01 AM > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > I rechecked quickly and I have different behaviors on different OSes. > > > *

Re: Configuring addresses starting with '/' on qpid-dispatch router 0.7.0

- Original Message - > From: "Olivier Mallassi" > To: users@qpid.apache.org > Cc: "Alan Conway" > Sent: Wednesday, March 29, 2017 3:30:48 PM > Subject: Re: Configuring addresses starting with '/' on qpid-dispatch router > 0.7.0 > > To

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

out. Thanks. > > -Ted > > On 04/04/2017 12:55 PM, Adel Boutros wrote: > > Hello Ganesh, > > > > > > I have applied your patch and it works as expected. > > > > > > Regarding Solaris, do you need extra information for analyzing? > > >

Re: Configuring addresses starting with '/' on qpid-dispatch router 0.7.0

- Original Message - > From: "Olivier Mallassi" > To: "Alan Conway" > Cc: "Rob Godfrey" , gmur...@redhat.com, > users@qpid.apache.org > Sent: Saturday, April 8, 2017 8:04:17 AM > Subject: Re: Configuring

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Regards, > > Adel > > > From: Ganesh Murthy <gmur...@redhat.com> > Sent: Monday, April 3, 2017 6:02:31 PM > To: users@qpid.apache.org > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > Hi Adel, > I

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

bindings activated. > > > > > PS: The good news is the code compiles on all 3 OSes but it's the tests which > are failing. We consider this as a big step forward compared to the previous > versions where the code didn't even compile on Solaris. > > > > > Re

Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

I think I have fixed all the license problems that Robbie pointed out. The code is now checked into master I added a file, .rat-excludes, to the base folder and it includes the js files whose licenses I have explicitly copied into the main LICENSE file. - Original Message - > From:

Re: [Qpid Proton] How mandatory is Cyrus for SASL

- Original Message - > From: "Ganesh Murthy" <gmur...@redhat.com> > To: users@qpid.apache.org > Sent: Friday, March 10, 2017 3:18:04 PM > Subject: Re: [Qpid Proton] How mandatory is Cyrus for SASL > > > > - Original Message - >

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

[Qpid Dispatch - 0.7.0] Random failure on unit test > "system_tests_link_routes" on Linux > > > No worries, it's ok :) > > > You will find attached the requested content. > > > Regards, > > Adel > > > From: Ganesh Mur

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

y 28, 2017 1:08:53 PM > Subject: Re: [Qpid Dispatch - 0.7.0] Random failure on unit test > "system_tests_link_routes" on Linux > > > > You will find attached the result of the below command. > > > > > Adel > > From: Ganesh Murthy <gmur

Re: [Qpid Dispatch - 0.7.0] Random failure on unit test "system_tests_link_routes" on Linux

test > "system_tests_link_routes" on Linux > > > It seems for some reason my mail wasn't sent. I am re-attaching the output > here. > > > Can you confirm you got it now? > > > Regards, > > Adel > > > From: G

Re: [Proton 0.16.0] [Dispatch Router 0.7.0] [Java Broker 6.0.4] [JMS 0.11.1] JMS sender's connection is being closed by the dispatch router

Hi Adel, Looking at the trace, there seems to be a framing error (ERROR amqp:connection:framing-error connection aborted) but it is not immediately clear what caused it. Sometimes, some other problem might manifest as a framing error, so I am not really sure. Are you able to replicate this in

Re: [Proton 0.16.0] [Dispatch Router 0.7.0] [Java Broker 6.0.4] [JMS 0.11.1] JMS sender's connection is being closed by the dispatch router

, Ganesh Murthy <gmur...@redhat.com> wrote: > Hi Adel, > Looking at the trace, there seems to be a framing error (ERROR > amqp:connection:framing-error connection aborted) but it is not immediately > clear what caused it. Sometimes, some other problem might manifest as a > f

Re: [Proton 0.16.0] [Dispatch Router 0.7.0] [Java Broker 6.0.4] [JMS 0.11.1] JMS sender's connection is being closed by the dispatch router

On Wed, Aug 2, 2017 at 12:42 PM, Adel Boutros wrote: > Hello, > > > As stated in a separate email, we are trying to compile Proton/Dispatch > router on Solaris using GCC4.9.2. The code compiles fine and all the unit > tests are green. > > > Hi Adel, If the code

Re: Dispatch Router load balancing config questions

Try setting the linkCapacity attribute of the listener. It is by default set to 250. The linkCapacity is the number of messages that can be in-flight concurrently for each link. Thanks. On Thu, Aug 10, 2017 at 5:59 PM, Dan Langford wrote: > thank you. as i configure

Re: Question about settled flag on a multi-frame transfer

ase you describe as meaning that the > delivery should be considered settled (and the Proton is behaving > incorrectly by the sounds of it). This interpretation is also reasonable > in the face of the definition of other fields on transfer such as "state". > > -- Rob > > On 5 Ju

Question about settled flag on a multi-frame transfer

I have a situation where a receiver (proton python's simple_recv.py) is receiving a multi-frame transfer from a Dispatch Router. The settled flag is false on all the transfer frames except on the last frame which has settled=true as seen here - https://pastebin.com/37SYrg92 Proton considers the

Re: [VOTE] Release Qpid Dispatch Router 0.8.0 (RC3)

+1 Verified signatures Unzipped tar file and compiled against proton 0.15, 0.17, master and ran successfully ran all unit tests Verified that all files have licenses after using the .rat-excludes file - Original Message - > From: "Ted Ross" > To: users@qpid.apache.org

Removal of deprecated items from the Dispatch Router schema

A few entities and attributes were deprecated in the 0.6.0 version of Qpid Dispatch Router. As we are coming up on a 1.0 release of the Router, we are going to be entirely removing these deprecated items from the router schema. Any Router code that helped support these deprecated items will also

Re: cmake install seems to tamper with interpreter directive

Should there be a Dispatch JIRA to fix this problem? On Wed, Sep 6, 2017 at 5:43 PM, Gordon Sim wrote: > On 06/09/17 22:11, Chris Richardson wrote: > >> autotools >> >> Unable to believe CMake could possibly be this rubbish (I am a devotee I'm >> afraid) I've just spent the

Re: [VOTE] Release Apache Qpid Proton 0.18.0

+1 Did the following - Downloaded the 0.18.0 source archive and verified signatures Compiled 0.18.0 source code Pointed Dispatch to use the 0.18.0 version of proton and all Dispatch unit tests executed successfully. Thanks. On Wed, Oct 18, 2017 at 1:29 PM, Robbie Gemmell

Re: On debian libsasl2-modules is needed when using the ANONYMOUS SASL mechanism

On Mon, Nov 27, 2017 at 6:54 AM, Alessio Gottardo wrote: > Hi guys, > > I am using: > - debian 9 (stretch) > - the Electron Go package wrapper fo Qpid proton-c > > I need to establish a TLS connection using the SASL ANONYMOUS mechanism > for AMQP. > I followed this

Re: [VOTE] Release Apache Qpid Proton 0.19.0

+1 * Validated signatures and checksums * Checked for presence of LICENSE and NOTICE files. * Compiled and installed it locally * Compiled and ran Qpid Dispatch unit tests successfully against this Proton. On Tue, Dec 19, 2017 at 4:17 PM, Robbie Gemmell wrote: > Hi

Re: [VOTE] Release Qpid Dispatch Router 1.0.0 (RC3)

+1 * Validated signatures and checksums * Checked for presence of LICENSE and NOTICE files * Ran mvn apache-rat:check, no missing license headers found. * Built from source and ran tests. All tests passed On Tue, Nov 14, 2017 at 9:01 AM, Ted Ross wrote: > Please cast your vote

Re: [VOTE] Release Apache Qpid Proton 0.18.1

+1 - verified checksums - built proton with Python binding set to ON - built Qpid Dispatch master branch against this proton - ran Dispatch tests successfully. On Tue, Oct 31, 2017 at 9:49 AM, Robbie Gemmell wrote: > Hi folks, > > I have put together a spin for a

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC2)

+1 * Validated signatures and checksums * Checked for presence of LICENSE and NOTICE files * Ran mvn apache-rat:check, no missing license headers found. * Built from source against Proton 0.22 in Fedora 27 and ran system tests. All tests passed On Tue, May 1, 2018 at 4:39 PM, Ganesh Murthy <g

[VOTE] Release Qpid Dispatch Router 1.1.0 (RC3)

Hello All, Please cast your vote on this thread to release RC3 as the official Qpid Dispatch Router version 1.1.0. RC3 of Qpid Dispatch Router version 1.1.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc3/ The following features, improvements, and

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC2)

lease policy > recommendation. > Thanks for pointing this out Robbie. I will make sure that the .md5 checksum is not included.anymore. > > I also raised DISPATCH-989 to cover some potentially stale symlinks > that remain in the tree. > > Robbie > > On 1 May 2018

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC2)

The vote is being extended for a couple more days to give time for people to test. Thanks. On Tue, May 1, 2018 at 4:39 PM, Ganesh Murthy <gmur...@apache.org> wrote: > Hello All, > > Please cast your vote on this thread to release RC2 as the > official Qpid Dispatch Rou

[VOTE] Release Qpid Dispatch Router 1.1.0 (RC4)

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 Router version 1.1.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc4/ The following features, improvements, and

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC4)

requires Proton 0.23.0 * Built from source against Proton 0.23.0 RC1 in Fedora 27 and ran system tests. All tests passed On Fri, May 25, 2018 at 5:45 PM, Ganesh Murthy <gmur...@apache.org> wrote: > Hello All, > > Please cast your vote on this thread to release RC4 as the

Re: Handling of undeliverable messages in Dispatch Router

On Thu, May 24, 2018 at 1:48 PM, Chuck Rolke wrote: > Releasing the messages sounds like the better choice. > > It also would be nice if the router could revoke the sender's credit so > that he could not send any more. This would create the same state as > when the sender

[VOTE] Release Qpid Dispatch Router 1.1.0 (RC5)

Hello All, Please cast your vote on this thread to release RC5 as the official Qpid Dispatch Router version 1.1.0. RC5 of Qpid Dispatch Router version 1.1.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc5/ The following features, improvements, and

[VOTE] Release Qpid Dispatch Router 1.1.0 (RC6)

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 version 1.1.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc6/ The following features, improvements, and

[CANCELED] [VOTE] Release Qpid Dispatch Router 1.1.0 (RC5)

but looking at the code in > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc5/, the fix > is > not in there. I'm not able to run the console from an http enabled > listener. > > > On Thu, Jun 7, 2018 at 3:23 PM, Ganesh Murthy wrote: > > > Hello A

[RESULT] [VOTE] Release Apache Qpid Dispatch 1.1.0

There were 6 binding +1 votes, 2 non-binding +1 votes and no other votes received. The vote has passed. I will add the files to the dist release repo and create the final tag shortly. The website will be updated after the release has had time to sync to the mirrors. Thanks to everybody for

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC6)

requires Proton 0.23.0 * Built from source against Proton 0.23.0 RC1 in Fedora 27 and ran system tests. All tests passed On Thu, Jun 7, 2018 at 5:01 PM, Ganesh Murthy wrote: > Hello All, > > Please cast your vote on this thread to release RC6 as the > official Qpid Dispatch Ro

[ANNOUNCE] Apache Qpid Dispatch 1.1.0 released

The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Dispatch 1.1.0 Qpid Dispatch is a router for the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It provides a flexible and scalable

Re: [VOTE CANCELED] Release Qpid Dispatch Router 1.1.0 (RC4)

o I'm going to bisect and see if > I can isolate the breaking change. > Stay tuned.... > > > On Fri, May 25, 2018 at 5:45 PM, Ganesh Murthy wrote: > > > Hello All, > > > > Please cast your vote on this thread to release RC4 as the > > official Qpid Disp

[VOTE] Release Qpid Dispatch Router 1.2.0 (RC2)

Hello All, Please cast your vote on this thread to release RC2 as the official Qpid Dispatch Router version 1.2.0. RC2 of Qpid Dispatch Router version 1.2.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.2.0-rc2/ The following features, improvements, and

Re: [VOTE] Release Apache Qpid Proton 0.24.0

+1 * Validated signatures and checksums * Checked for presence of LICENSE and NOTICE files * Compiled source and ran tests against Qpid Dispatch master and all tests pass * Compiled and ran tests against Qpid Dispatch 1.1.0. The policy tests fail but that is because of stricter UIRL parsing

[RESULT] [VOTE] Release Apache Qpid Dispatch 1.2.0

There were 8 binding +1 votes, 1 non-binding +1 votes and no other votes received. The vote has passed. I will add the files to the dist release repo and create the final tag shortly. The website will be updated after the release has had time to sync to the mirrors. Thanks to everybody for

Re: [VOTE] Release Qpid Dispatch Router 1.2.0 (RC2)

+1 * Validated signatures and checksums * Checked for presence of LICENSE and NOTICE files * Ran mvn apache-rat:check, no files with missing license headers found. * Built from source against Proton 0.24.0 in Fedora 27 and ran system tests. All tests passed On Fri, Jun 29, 2018 at 3:21 PM, Ganesh

[VOTE] Release Qpid Dispatch Router 1.1.0 (RC2)

Hello All, Please cast your vote on this thread to release RC2 as the official Qpid Dispatch Router version 1.1.0. RC2 of Qpid Dispatch Router version 1.1.0 can be found here - https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.1.0-rc2/ The following features, improvements, and

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC2)

orrect > version. > > ----- Original Message - > > From: "Ganesh Murthy" <gmur...@apache.org> > > To: users@qpid.apache.org > > Sent: Tuesday, May 1, 2018 4:39:25 PM > > Subject: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC2) > > > > He

  1   2   3   >