On Sat, Feb 16, 2013 at 12:51 PM, Paul O'Fallon wrote:
> Hello! At the risk of revealing my atrophied C skills, I have a question
> about the recv.c Messenger example which contains this block of code:
>
> size_t buffsize = 1024;
> char buffer[buffsize];
> pn_data_t *body = pn_message_body(messag
[
https://issues.apache.org/jira/browse/PROTON-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580317#comment-13580317
]
michael goulish commented on PROTON-200:
I think this bug is a release blocker.
A
Not immediately obvious from the Jira, but PROTON-200 means that if you set up
a simple topology -- one receiver, two senders -- the second sender will block
until the first one calls 'stop'. This is still true in 0.4 RC1.
I think that needs to be fixed before release.
[
https://issues.apache.org/jira/browse/PROTON-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580326#comment-13580326
]
Bozo Dragojevic commented on PROTON-200:
For us we could not do anything except 1:
If I kill send.c while it's sending the messages then recv output might
look like this:
$ ./recv
.
1361144306.723531
Address: amqp://0.0.0.0
Subject: Greetings from send 24136
Content: "Hello World!"
### engine.c:1395 pn_do_error ERROR ### transport-5 ERROR
amqp:connection:fram
