It looks like the actual issue has been identified on another thread, but
while this is here...I noticed that the mechanisms are in a different order
between the two snippets below, however the 1.0 spec indicates they are to
be ordered in decreasing level of preference which I would expect to make
A related question regarding subscription API. There are several use cases.
A single subscription to invalid queue on a running broker, the messenger is
blocking
pn_messenger_subscribe(messenger,
amqp://guest:guest@127.0.0.1:5772/testqueue2);
pn_messenger_rewrite(messenger, amqp://%/*, $2);
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
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
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
Hello. I am evaluating Qpid Proton AMQP Messenger to communicate with
SwiftMQ broker. I've had issues with receiving messages, but I used
suggestion here https://issues.apache.org/jira/browse/PROTON-484 and it
solved the problem. The use case I am testing is broker is down. Modified
send.c
Hi,
Welcome to the list.
The put and send return codes are used for more basic errors, e.g. coding
errors. Tracking the status of outgoing messages has it's own API similar
to the one you've already used in your receiver. Below is a rough example.
I've omitted the return code checking for
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
