Qpid proton C++ supports failover url?

[adelboutros]

Hello,


Does the Proton C++ API support the failover url just like JMS does?

If no, what workarounds could I use?


Regards,

Adel


Get Outlook for Android

RE: [JAVA-Android]Memory Leak Investigation

[adelboutros]

PS: don't use nabble when you send a mail because half of it is missing when we 
receive it.


As for the Azure part, unfortunately I cannot help you because I never used it. 
Hopefully someone else will be able to.




On Fri, Jul 29, 2016 at 7:45 PM +0300,  wrote:







If A holds a reference to B and B holds a reference to A. Then you will get 
this cyclic tree when you open A.


Try opening the "referent" instead of the "runner" in the second image.



From: kevin.le

Sent: Friday, July 29, 18:53

Subject: RE: [JAVA-Android]Memory Leak Investigation

To: users@qpid.apache.org



Thanks for the quick reply Adel.


Tried your suggestion. Here are some screengrabs:








Looking at the second image, I could not understand it. The reference tree

jumps to and fro between two references forever if I open any of the tree.


What do you advise?






--

View this message in context: 
http://qpid.2158936.n2.nabble.com/JAVA-Android-Memory-Leak-Investigation-tp7648353p7648365.html

Sent from the Apache Qpid users mailing list archive at Nabble.com.


-

To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org

For additional commands, e-mail: users-h...@qpid.apache.org

RE: [JAVA-Android]Memory Leak Investigation

[adelboutros]

If A holds a reference to B and B holds a reference to A. Then you will get 
this cyclic tree when you open A.


Try opening the "referent" instead of the "runner" in the second image.



From: kevin.le

Sent: Friday, July 29, 18:53

Subject: RE: [JAVA-Android]Memory Leak Investigation

To: users@qpid.apache.org



Thanks for the quick reply Adel.


Tried your suggestion. Here are some screengrabs:


 


 


Looking at the second image, I could not understand it. The reference tree

jumps to and fro between two references forever if I open any of the tree. 


What do you advise?






--

View this message in context: 
http://qpid.2158936.n2.nabble.com/JAVA-Android-Memory-Leak-Investigation-tp7648353p7648365.html

Sent from the Apache Qpid users mailing list archive at Nabble.com.


-

To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org

For additional commands, e-mail: users-h...@qpid.apache.org

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

[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(2000);


   handler.close();



Thread 2:


   proton::container(handler).run();



Regards,


Adel


 

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

[adelboutros]

Hello guys,



We were able to advance on this issue by changing the machine and using one 
with less security restraints.



Now we have the following issues:



1) A missing powershell script(run_queue_redirect.ps1) forces a test 
(queue_redirect) not to start 



2) Python scripts can be executed on Linux without adding "python" prior to the 
script name because it is detected from the first line in the script 
(#!/usr/bin/env python). This doesn't work on Windows unless "py" extension 
files are associated with python. To do this, all python scripts must end with 
.py which is not the case for a lot of the scripts such as the qpidd management 
tools (qpid-python-test, qpid-config, ...)



So we wanted to know if you could help us fix the above issues?



We are currently debugging other issues as well and wanted to ask you to 
confirm that some of the tests actually requires the management tools installed 
as a pre-requisite?



Regards,


Adel



From: Rabih M

Sent: Wednesday, May 18, 16:54

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

To: users@qpid.apache.org



Hello,


I compiled the Qpid C++ code on windows using visual studio 2013.

I have some unit tests failures, I tried to debug but it is not obvious to

find the root cause.


In qpid-client-test: The client is not able to connect to the qpid broker.

This the output I am getting:

...

test 1

    Start 1: qpid-client-test


1: Test command: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

D:/qpid-cpp-0.34/qpid-cpp-0.34/qpid/cpp/src/tests/run_test.ps1 -buildDir

D:/qpid-cpp-0.34/qpid-cpp-0.34/qpid/cpp/build-dir -startBroker --

D:/qpid-cpp-0.34/qpid-cpp-0.34/qpid/cpp/build-dir/src/tests/qpid-client-test.exe

1: Test timeout computed to be: 1500

1: 2016-05-18 16:46:39 [Broker] notice Broker (pid=10372) start-up

1: 2016-05-18 16:46:39 [Broker] notice SASL disabled: No Authentication

Performed

1: 2016-05-18 16:46:39 [Security] notice Listening for SSL connections on

TCP port 5671

1: 2016-05-18 16:46:39 [Network] notice Listening on TCP/TCP6 port 21077

1: 2016-05-18 16:46:40 [Network] warning Connect failed: No connection

could be made because the target machine actively refused it. :

localhost:21077

(D:\qpid-cpp-0.34\qpid-cpp-0.34\qpid\cpp\src\qpid\sys\windows\WinSocket.cpp:164)

1: Connection  closed

1: WARNING: suspicious log entries in


D:\qpid-cpp-0.34\qpid-cpp-0.34\qpid\cpp\build-dir\src\tests\qpid-client-test.log:1:2016-05-18

16:46:40 [Network] warning Connect failed: No connection could be made

because the target machine actively refused it. : localhost:21077

(D:\qpid-cpp-0.34\qpid-cpp-0.34\qpid\cpp\src\qpid\sys\windows\WinSocket.cpp:164)

1: 2016-05-18 16:46:40 [Broker] notice Broker (pid=10372) shut-down

1/1 Test #1: qpid-client-test .***Failed    2.15 sec


Did anyone encountered this error before?

The firewall on the machine is off. And I verified using netstat that the

port 21077 was open and listening.



Thanks,

Rabih

Re: [Qpid Dispatcher] Runtime behavior on SunOS

[adelboutros]

Thanks Andrew! We were also amazed at the fact it was a POLLOUT but it's not 
the first time Solaris has an inexplicable behavior ...


I will try to fix the code to ignore Pollout flag and let you know if it works.


Would it interest you if i provide a patch also in case it works?



Sent from Outlook Mobile



From: Andrew Stitcher

Sent: Wednesday, April 20, 19:31

Subject: Re: [Qpid Dispatcher] Runtime behavior on SunOS

To: users@qpid.apache.org



On Wed, 2016-04-20 at 08:03 -0700, Adel Boutros wrote:

> Here they are:

> 

> Solaris:

> 1)  qdpn_driver_wait_3:  idx=2, d->fds[idx].revents=*4*, POLLIN=1

> *Test dies here*


revents=4 seems to be POLLOUT.


Since this is the read end of a pipe (if I understood correctly) I'm

not sure why POLLOUT is true, or even why that bit is in the interest

set. But in any case it can just be ignored as dispatch is never going

to write to the read end of the pipe.


Andrew



-

To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org

For additional commands, e-mail: users-h...@qpid.apache.org