Out of curiosity which version of Proton are you using? I *think* that's
a fairly recent fix.
I was seeing something similar in my asynchronous experiments (I needed
to figure out when the message actually reached the receiver so I could
hold off terminating my async producer until then) and Rafael put a fix
onto Proton trunk - that'd be ~3-4 weeks ago.
It might be worth you trying a build off trunk.
Regards,
Frase
On 10/01/14 22:43, serega wrote:
Thanks for your reply. I added the tracker, but with the same scenario it
returns 0 which is PN_STATUS_UNKNOWN = 0.
-------------------------------------------------------------
Error 0
read: Connection refused
[0x100810800:0] ERROR[-2] SASL header mismatch: ''
send: Broken pipe
CONNECTION ERROR connection aborted
Error 0
Status off M1: 0
-----------------------------------------------------------
It looks like internally messenger prints error messages, but it doesn't
communicate with the client about the error. The unknown status isn't very
meaningful.
Sergey.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/pn-messenger-send-return-code-tp7602570p7602587.html
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
