You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by rajinisivaram <gi...@git.apache.org> on 2016/05/09 10:11:21 UTC

[GitHub] kafka pull request: KAFKA-3662: Fix timing issue in SocketServerTe...

GitHub user rajinisivaram opened a pull request:

    https://github.com/apache/kafka/pull/1349

    KAFKA-3662: Fix timing issue in SocketServerTest.tooBigRequestIsRejected

    Test sends large request using multiple writes of length followed by request body. The first write should succeed, but since the server closes the connection on processing the length that is too big, subsequent writes may fail. Modified test to handle this exception.

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

    $ git pull https://github.com/rajinisivaram/kafka KAFKA-3662

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

    https://github.com/apache/kafka/pull/1349.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 #1349
    
----
commit 632c7427341a3d39cb35a3c21f0532440fe0815a
Author: Rajini Sivaram <ra...@googlemail.com>
Date:   2016-05-09T10:04:41Z

    KAFKA-3662: Fix timing issue in SocketServerTest.tooBigRequestIsRejected

----


---
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.
---

[GitHub] kafka pull request: KAFKA-3662: Fix timing issue in SocketServerTe...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/1349


---
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.
---