[ 
https://issues.apache.org/jira/browse/ARTEMIS-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094382#comment-16094382
 ] 

ASF GitHub Bot commented on ARTEMIS-1301:
-----------------------------------------

GitHub user franz1981 opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1412

    ARTEMIS-1301 Network failures recognition on backpressure while streaming 
large messages

    NettyConnection's flow control provides backpressure while streaming large 
messages without taking in account disconnection/network failures: it is needed 
to recognize connection failures and react to them.
    
    The fix allows NettyConnection (and CoreRemotingConnection too) to 
recognize a network failure while being backpressured and to fail fast while 
streaming large messages.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/franz1981/activemq-artemis 
slow_large_msg_streaming

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1412.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1412
    
----
commit 32fe21d59591788f67cbb65d7cb7e641f74c44d1
Author: Francesco Nigro <[email protected]>
Date:   2017-07-18T11:31:35Z

    ARTEMIS-1301 Network failures recognition on backpressure while streaming 
large messages

----


> Network failures recognition on backpressure while streaming large messages
> ---------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1301
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1301
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>
> NettyConnection's flow control provides backpressure while streaming large 
> messages without taking in account disconnection/network failures: it is 
> needed to recognize connection failures and react to them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to