Brian Bouterse commented on PROTON-1515:

I've experienced something very similar to this issue. In my case I did this:

1. Start broker and proton client
2. Create queue
3. Kill broker
4. Try to send a message.

Specifically this bug articulates that a link error for messages already 
received should be raised as soon as possible. I agree with that. My slight 
addition is that link state should also be checked when accepting messages to 
be sent. When my code calls sender.send(the_message) I am requesting an 
exception to be raised then by checking the link state.

Should this be its own bug or just an aspect to the fix for this bug?

> Python sender client doesn't check actual link state and continues to send 
> messages even if link is down
> --------------------------------------------------------------------------------------------------------
>                 Key: PROTON-1515
>                 URL: https://issues.apache.org/jira/browse/PROTON-1515
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: python-binding
>         Environment: RHEL7.3
> Jboss AMQ 7
> python-qpid-proton.x86_64-0.14.0-1.el7
>            Reporter: Dmitrii Puzikov
>         Attachments: sender.log
> Steps to reproduce:
> 1. Start broker
> 2. Create queue
> 3. Start sending e.g. 10 messages with python sender
> 4. Kill broker
> 5. Notice that client continues send messages and raises exception only after 
> all 10 messages were sent.
> Actual behavior: Python sender client ignores link failure until all messages 
> were sent and only then raises an exception/ begins re-connection attempmts.
> Expected behavior: Client should stop sending messages and raise exception or 
> try to begin re-connection attempts if reconnect option is set.
> Please, see sender.log. Global handler was added for event logging purposes. 
> It just prints event/handler name.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to