McClements
Subject: Re: Deadlock in pn_messenger_stop? (C Qpid Library)
Go ahead and raise a ticket for it and attach the reproducer. I'm currently
banging my head against another bug, but I'll take a look as soon as my
head or the other bug gives way. ;-)
--Rafael
On Sat, Jun 22, 2013 at 7:09
irm that this is an issue? Should I raise a ticket for this?
>
> Cheers,
> Frank
>
> - Original Message -
> From: Frank Quinn
> Sent: Friday, June 14, 2013 06:03 PM
> To: 'proton@qpid.apache.org'
> Cc: Damian Maguire; Glenn McClements
> Subject:
Hi, Frank.
I just had the similar problem. In my case I'm trying to call
pn_messenger_stop and the thread hangs. I have only one main thread. So, it
seems to be a bug.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Deadlock-in-pn-messenger-stop-C-Qpid-Library-tp7594142p7594
s with the
same backtrace as originally reported when trying to run pn_messenger_stop.
Cheers,
Frank
-Original Message-
From: Frank Quinn
Sent: 14 June 2013 13:49
To: proton@qpid.apache.org
Subject: RE: Deadlock in pn_messenger_stop? (C Qpid Library)
Thanks Ted,
I did try inserting a s
backtrace as originally reported when trying to run pn_messenger_stop.
Cheers,
Frank
-Original Message-
From: Frank Quinn
Sent: 14 June 2013 13:49
To: proton@qpid.apache.org
Subject: RE: Deadlock in pn_messenger_stop? (C Qpid Library)
Thanks Ted,
I did try inserting a sleep of 1s between the
still unsure why, but I'll not question it for now), thanks!
Cheers,
Frank
-Original Message-
From: Ted Ross [mailto:tr...@redhat.com]
Sent: 14 June 2013 13:09
To: proton@qpid.apache.org
Subject: Re: Deadlock in pn_messenger_stop? (C Qpid Library)
I would suggest that you no
I would suggest that you not stop the subscriber messenger in the main
thread. Rather, stop it in the subscriber thread right before it
exits. Alternatively (preferably), you should pthread_join the thread
in main before stopping the messengers.
It looks to me that you've got a race conditio
