[
https://issues.apache.org/jira/browse/PROTON-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867634#comment-13867634
]
Andreas Mueller commented on PROTON-484:
This is what you send when attaching a
Am 09.01.2014 um 21:15 schrieb Rafael Schloming r...@alum.mit.edu:
What we have is currently available here:
http://qpid.apache.org/components/messenger/index.html
It is probably a bit more developed for the python binding than for the C
API itself. Certainly accessing/manipulating data
[
https://issues.apache.org/jira/browse/PROTON-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867694#comment-13867694
]
Rafael H. Schloming commented on PROTON-484:
Ah, I understand now, thanks for
[
https://issues.apache.org/jira/browse/PROTON-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim closed PROTON-426.
-
Resolution: Duplicate
[Messenger] messenger has no ability to dynamically create queues/topics on
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
