ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dmagda <...@git.apache.org>
Subject [GitHub] ignite pull request: Ignite 1294: Assertion in TCP communication S...
Date Fri, 28 Aug 2015 10:39:15 GMT
GitHub user dmagda opened a pull request:

    https://github.com/apache/ignite/pull/45

    Ignite 1294: Assertion in TCP communication SPI: client already created

    The following bugs were found and fixed:
    
    - fixed a bug when a Future wasn't completed in NIO Server listener. This might cause
hangs when a TCP client is being created locally;
    
    - fixed a race condition between shmem and TCP communication clients. Sometimes a NIO
server listener could create a TCP client while shmem client creation was in progress.


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

    $ git pull https://github.com/dmagda/incubator-ignite ignite-1294

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

    https://github.com/apache/ignite/pull/45.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 #45
    
----
commit 30482cdc02e2e0261818d0a543641cba2536aae2
Author: Denis Magda <dmagda@gridgain.com>
Date:   2015-08-28T08:11:50Z

    ignite-1294: minor fixes and improvements in the processing of incoming SPI communication
session

commit c3adde0386d94f899c65787b8e377206d4e30775
Author: Denis Magda <dmagda@gridgain.com>
Date:   2015-08-28T10:27:18Z

    ignite-1294: fixed the race between 'outgoing' shmem connection and incoming TCP connection

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message