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

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

GitHub user clebertsuconic opened a pull request:

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

    ARTEMIS-1269 Fixing blocked replication

    If replication blocked anything on the journal
    the processing from clients would be blocked
    and nothing would work.
    
    As part of this fix I am using an executor on ServerSessionPacketHandler
    which will also scale better as the reader from Netty would be feed 
immediately.

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

    $ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS-1269

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

    https://github.com/apache/activemq-artemis/pull/1386.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 #1386
    
----
commit c66b98a53827e0b8e07cc8dad8a1140f07026af8
Author: Clebert Suconic <[email protected]>
Date:   2017-07-05T17:28:01Z

    ARTEMIS-1269 Fixing blocked replication
    
    If replication blocked anything on the journal
    the processing from clients would be blocked
    and nothing would work.
    
    As part of this fix I am using an executor on ServerSessionPacketHandler
    which will also scale better as the reader from Netty would be feed 
immediately.

----


> Replication Initial Synchronization won't finish sometimes
> ----------------------------------------------------------
>
>                 Key: ARTEMIS-1269
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1269
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.5.5, 2.1.0
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>             Fix For: 1.5.6, 2.2.0
>
>




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

Reply via email to