[jira] [Updated] (PROTON-1515) Python sender client doesn't check actual link state and continues to send messages even if link is down
[ https://issues.apache.org/jira/browse/PROTON-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated PROTON-1515: --- Description: 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 attempts. 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. was: 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. > 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 >Assignee: Justin Ross >Priority: Major > Fix For: proton-c-0.21.0 > > 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 attempts. > 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 (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1515) Python sender client doesn't check actual link state and continues to send messages even if link is down
[ https://issues.apache.org/jira/browse/PROTON-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1515: Fix Version/s: (was: proton-c-0.19.0) proton-c-0.20.0 > 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 >Assignee: Justin Ross > Fix For: proton-c-0.20.0 > > 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 (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1515) Python sender client doesn't check actual link state and continues to send messages even if link is down
[ https://issues.apache.org/jira/browse/PROTON-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1515: Fix Version/s: proton-c-0.19.0 > 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 > Fix For: proton-c-0.19.0 > > 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 (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
