Re: RFI 0.13: Blocker PROTON-1216 c++: proton::coerce() should allow conversion from binary.

2016-06-01 Thread Andrew Stitcher
On Tue, 2016-05-31 at 13:50 -0400, Alan Conway wrote: > Andrew can you approve this? > > https://issues.apache.org/jira/browse/PROTON-1216 > > Approved as a whole - please squash all the master changes before adding to the release branch, Andrew --

[proton-c 0.12.0] SASL unit test are failing

2016-06-01 Thread Rabih M
Hello, I tried to launch proton 0.12.0 unit tests on Linux, everything is working fine except when i launch SASL related unit tests in python-test. The following 2 tests are failing when SASL is activated but are passing when SASL is deactivated: proton_tests.engine.SaslEventTest.testPipelinedSe

Re: Qdstat, SASL and user with @domain

2016-06-01 Thread Ganesh Murthy
- Original Message - > From: "Gordon Sim" > 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: > > There is a dispatch issue > > https://issues.apache.org/jira/browse/D

[Proton-c] Closing connection of proton::handler from outside the callbacks

2016-06-01 Thread adelboutros
Hello, In proton 0.12.0 C++ bindings, if I have a custom handler which implements proton::handler, how can I close the connection it holds from outside the callbacks? (Callbacks like on_message, on_link_open, etc.) Thread 1:    CustomHandler handler;    // Start Thread 2    sleep(200

Re: Qdstat, SASL and user with @domain

2016-06-01 Thread Gordon Sim
On 01/06/16 17:05, Ganesh Murthy wrote: There is a dispatch issue https://issues.apache.org/jira/browse/DISPATCH-233 which will deal with exactly what you are talking about. The fix to DISPATCH-233 will be available in 0.7 release. So for 0.6 you can't use qdstat on a router using sasldb

RE: Qdstat, SASL and user with @domain

2016-06-01 Thread Paolo Patierno
Hi Ganesh, thanks ! Paolo. Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoTMicrosoft Azure Advisor Twitter : @ppatierno Linkedin : paolopatierno Blog : DevExperience > Date: Wed, 1 Jun 2016 12:05:38 -0400 > From: gmur...@redhat.com > To: users@qpid.

Re: Qdstat, SASL and user with @domain

2016-06-01 Thread Ganesh Murthy
Hi Paolo, There is a dispatch issue https://issues.apache.org/jira/browse/DISPATCH-233 which will deal with exactly what you are talking about. The fix to DISPATCH-233 will be available in 0.7 release. Thanks. - Original Message - > From: "Paolo Patierno" > To: users@qpid.apache.org

Qdstat, SASL and user with @domain

2016-06-01 Thread Paolo Patierno
Hi all, I have configured a router with SASL PLAIN authentication and the SASL db was created using the Cyrus tool (saslpasswd2). Using this tool you can specify or not a domain but if you don't specify it, the tool adds a default one (the machine hostname on which it's running). In any case you

RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013

2016-06-01 Thread Adel Boutros
I am taking a look at the failures I have for all the tests. I have the same failures as you do plus the 2 below: interlink_tests In some of the tests, you use the option "--socket-fd" which is not recognized on Windows. [Broker] critical Unexpected error: Error in command line options: unrecogni

Re: Lock-up in waitForCompletion()

2016-06-01 Thread Toralf Lund
On 01/06/16 10:27, Gordon Sim wrote: On 01/06/16 08:47, Toralf Lund wrote: Hi, I haven't had time to look at this again until now... I restarted qpidd the on the (current) backup server, and after that, I can't reproduce the issue. I guess this means it was indeed related to replication. Unfor

RE: Qpid C++ 0.34 unit tests are failing with visual studio 2013

2016-06-01 Thread Adel Boutros
Hello Justin, I took a look at the appveyor link you sent and there 2 issues which I wanted to raise:In your cmake, Proton is not found (Some of the tests are skipped or disabled)SWIG is not present (I believe it is also used in the tests) This is why you have only 12 total tests while I have 15

Re: Lock-up in waitForCompletion()

2016-06-01 Thread Gordon Sim
On 01/06/16 08:47, Toralf Lund wrote: Hi, I haven't had time to look at this again until now... I restarted qpidd the on the (current) backup server, and after that, I can't reproduce the issue. I guess this means it was indeed related to replication. Unfortunately, I never managed to enable pr

Re: Lock-up in waitForCompletion()

2016-06-01 Thread Toralf Lund
Hi, I haven't had time to look at this again until now... I restarted qpidd the on the (current) backup server, and after that, I can't reproduce the issue. I guess this means it was indeed related to replication. Unfortunately, I never managed to enable protocol trace so I could verify it. H