I think the SASL error below might be caused by occasionally using an unsupported SASL mechanism. I don't know where to set the mechanism in Messenger. If you find how, set it to "PLAIN" or "CRAM-MD5".
Andreas > Am 12.01.2014 um 04:34 schrieb serega <sergejs.melde...@sap.com>: > > I didn't insert the line in the code as was suggested by Rafael > pn_messenger_set_outgoing_window(messenger, N); > > With that change I get PN_STATUS_ABORTED = 6 when the link is broken. > > I do have another problem though. I get the following errors sometimes.. > > ./send -a amqp://guest:guest@127.0.0.1:5672/testqueue > [0x7fdf48700a10]:ERROR[-2] SASL header mismatch: > '\x00\x00\x00\x17\x02\x01\x00\x00\x00\x80\x00\x00\x00\x00\x00\x00\x00D\xc0\x03\x01P\x00AMQP\x03\x01\x00\x00\x00\x00\x00B\x02\x01\x00\x00\x00\x80\x00\x00\x00\x00\x00\x00\x00@\xc0.\x01\xe0+\x05\xa3\x04NTLM\x05PLAIN\x09ANONYMOUS\x0aDIGEST-MD5\x08CRAM-MD5' > > > sergey:Debug sergey$ for i in {1..5000} ; do ./send -a > amqp://guest:guest@127.0.0.1:5672/testqueue; done > [0x7fb0c1406670]:ERROR[-2] SASL header mismatch: > '\x00\x00\x00\x17\x02\x01\x00\x00\x00\x80\x00\x00\x00\x00\x00\x00\x00D\xc0\x03\x01P\x00AMQP\x03\x01\x00\x00\x00\x00\x00B\x02\x01\x00\x00\x00\x80\x00\x00\x00\x00\x00\x00\x00@\xc0.\x01\xe0+\x05\xa3\x0aDIGEST-MD5\x08CRAM-MD5\x04NTLM\x05PLAIN\x09ANONYMOUS' > > > The client simply hangs after reporting this error. I stepped in debugger > and found that the call doesn't return from pn_driver_wait(). > > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/pn-messenger-send-return-code-tp7602570p7602616.html > Sent from the Apache Qpid Proton mailing list archive at Nabble.com. IIT Software GmbH Fahrenheitstr. 13, D28359 Bremen, Germany Tel: +49 421 330 46 088, Fax: +49 421 330 46 090 Amtsgericht Bremen, HRB 18624, Geschaeftsfuehrer: Andreas Mueller Steuernummer: 460/118/06404 VAT: DE199945912