Please just create the JIRA already... [Was proton cpp container.stop not fully thread safe]

2019-04-04 Thread Andrew Stitcher
As a matter of policy, it is much better to just create the Jira based on the symptoms and update it as more info becomes known than to front load the process before creating the jira. This is a general point and not restricted to this issue. Yes, I know that I'm as likely to fall foul of this as

Re: proton cpp container.stop not fully thread safe

2019-04-03 Thread Cliff Jansen
I can reproduce and it looks more like a proactor problem than the C++ container.stop(). I will investigate further and create an appropriate JIRA. Thank you for the simple test case. Cliff On Wed, Apr 3, 2019 at 4:17 AM Rabih M wrote: > > Hello, > > Concerning this point, i still have the sam

Re: proton cpp container.stop not fully thread safe

2019-04-03 Thread Rabih M
Hello, Concerning this point, i still have the same crash even after modifying the code to be thread safe. I attached the corrected code. If i add a sleep of 50 ms before stopping the container everything works correctly. I think there is a concurrency problem somewhere in the proton code. Do yo

proton cpp container.stop not fully thread safe

2019-03-27 Thread Rabih M
Hello, I am using proton cpp version 0.27.0. I have a random crash when calling stop on the container after closing the connection. Please find the attached the code and the stack. In the doc, it is said that the container object is thread safe but apparently there is flaw... Can you please advi