You can recreate this on a CentOS 6.6 box by installing qpid-proton-c-devel using yum from EPEL, then compiling the example application that comes with it in /usr/share/proton/examples/messenger/send.c.
There is no broker with these example applications - it's point to point. There is a matching recv.c application there too. If you start recv first, it works fine, but if you don't, the send application hangs which I believe is new behaviour. Again, this does not happen on my Fedora laptop - only on CentOS 6. Cheers, Frank On Wed, Jun 10, 2015 at 1:34 PM, Darryl L. Pierce <dpie...@redhat.com> wrote: > On Tue, Jun 09, 2015 at 10:41:51PM +0100, Frank Quinn wrote: > > Just tried this and can recreate on a 64 bit laptop running CentOS 6.6 > > natively too. The send application never exits if a receiver is not yet > > ready. Can anyone else see this or am I going mad? > > Are these bits you've built or did you install them from RPM (not sure > if you said before, so please remind me)? And are you running a Qpid or > other broker? I ask because it seems you're getting a connection (no > "connection refused" error) but something else is causing the failure, > the SASL header mismatch. > > How is your SASL configuration setup on the broker to which you're > connecting? > > -- > Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > Delivering value year after year. > Red Hat ranks #1 in value among software vendors. > http://www.redhat.com/promo/vendor/ > >
