Re: [VOTE] Release Apache Qpid Proton 0.18.0

2017-10-18 Thread Timothy Bish
+1 * Validated signature and checksum * Verified License and Notice files present * Built from source and ran self tests. On 10/18/2017 01:29 PM, Robbie Gemmell wrote: Hi folks, I have put together a first spin for a Qpid Proton 0.18.0 release, please test it and vote accordingly. The source

Re: [VOTE] Release Apache Qpid Proton 0.18.0

2017-10-18 Thread Chuck Rolke
+1 * Verified checksums * Built debug on Fedora 25 ** Self tests pass * Included in Dispatch ** Dispatch self tests pass * Build Visual Studio 2013 x64 ** Self tests pass Debug, Release - Original Message - > From: "Robbie Gemmell" > To: users@qpid.apache.org > Sent: Wednesday, October

Qpid Dispatch Router 1.0.0 Release Candidate

2017-10-18 Thread Ted Ross
Team, RC1 of Qpid Dispatch Router version 1.0.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.0.0-rc1/ Please use this for testing and evaluation. I will hold off the vote until there has been some testing done. There have already been some minor console issues

Re: [VOTE] Release Apache Qpid Proton 0.18.0

2017-10-18 Thread Ganesh Murthy
+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 wrote: > Hi folks, > >

Re: Exchanges usage

2017-10-18 Thread Robbie Gemmell
It is possible to either 'subscribe' to the exchange itself (with the broker possibly making tempory subscription queues in the background to facilitate it), or explicitly bind queues to exchanges (which can be done with qpid-configs bind and unbind subcommands) and then consume from the queues. Th

[VOTE] Release Apache Qpid Proton 0.18.0

2017-10-18 Thread Robbie Gemmell
Hi folks, I have put together a first spin for a Qpid Proton 0.18.0 release, please test it and vote accordingly. The source archive can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.18.0-rc1/ The JIRAs currently assigned are: https://issues.apache.org/jira/secure/Release

Re: [Qpid Java Broker 6.1.4] Some expections are hidden

2017-10-18 Thread Adel Boutros
Sorry Keith but I didn't have enough time to create the Jira or provide a fix :( From: Keith W Sent: Wednesday, October 18, 2017 7:02:40 PM To: users@qpid.apache.org Subject: Re: [Qpid Java Broker 6.1.4] Some expections are hidden I raised this as QPID-7979. On

Re: [Qpid Java Broker 6.1.4] Some expections are hidden

2017-10-18 Thread Keith W
I raised this as QPID-7979. On 16 October 2017 at 12:34, Keith W wrote: > Hi Adel > > Please raise a JIRA. Include a patch or pull request if you like. > I'll try to include in v7.0. > > cheers Keith > > On 16 October 2017 at 12:06, Adel Boutros wrote: >> No, this was the only case I hit while

Exchanges usage

2017-10-18 Thread Michael Ivanov
Greetings, Can somebiody point me to proper qpidd exchange configuration? I want to use some kind of broadcast messages delivered to several subscribers simultaneously. For this I create an fanout exchange with specific name and make all subscribers to subscribe to this exchange name, same way as

Re: SASL PLAIN Tokens and Golang Question

2017-10-18 Thread Alan Conway
The problem is confusion between URL and Go "connection address". Electron lets Go do all the networking and only handles AMQP encoding/decoding, so electron.Container.Dial() is just a shortcut for conn := net.Dial(...); proton.Container.Connection(conn, [options...]) So the network address to Dia

[Qpid Java Broker 6.1.4] JDBC fixes

2017-10-18 Thread Adel Boutros
Hello guys, While testing the tableNamePrefix, we noticed a bug and a very slow performance on Oracle Database. I have submitted 2 jiras one for each and a pull request on the master of qpid-broker-j. So I was wondering if they are accepted if it is possible to backport them to 6.1 branch a

RE: SASL PLAIN Tokens and Golang Question

2017-10-18 Thread Clemens Vasters
A forward-slash '/' as the username and password separator is a surprise, because [1] and more importantly [2] Note: The rule in the quoted Proton-C doc formally disallows any occurrence of '/' for the password, but it doesn't enforce it [3] so base64-encoded (with '/') strings are factually wo