You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/21 22:47:00 UTC

[jira] [Commented] (APEXCORE-748) Upgrade netlet dependency to 1.3.2

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

ASF GitHub Bot commented on APEXCORE-748:
-----------------------------------------

GitHub user vrozov opened a pull request:

    https://github.com/apache/apex-core/pull/548

    APEXCORE-748 Upgrade netlet dependency to 1.3.2

    

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

    $ git pull https://github.com/vrozov/apex-core APEXCORE-748

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

    https://github.com/apache/apex-core/pull/548.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 #548
    
----
commit 3ddd2389f7e52cbca82370b1f77377b083f4aa44
Author: Vlad Rozov <vr...@apache.org>
Date:   2017-06-21T22:37:56Z

    APEXCORE-748 Upgrade netlet dependency to 1.3.2

----


> Upgrade netlet dependency to 1.3.2
> ----------------------------------
>
>                 Key: APEXCORE-748
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-748
>             Project: Apache Apex Core
>          Issue Type: Dependency upgrade
>            Reporter: Vlad Rozov
>            Assignee: Vlad Rozov
>            Priority: Minor
>
> There is a regression introduced in netlet 1.3.1 that may lead to two or more netlet event loops running at the same time. Such condition leads to incorrect netlet behavior. The bug is specific to Apex local mode and unit tests where multiple containers run in the same JVM (different threads)



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