[
https://issues.apache.org/jira/browse/ZOOKEEPER-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653202#comment-13653202
]
Hadoop QA commented on ZOOKEEPER-1702:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12582508/ZOOKEEPER-1702.1.patch
against trunk revision 1463329.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1475//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1475//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1475//console
This message is automatically generated.
> ZooKeeper client may write operation packets before receiving successful
> response to connection request, can cause TCP RST
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1702
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1702
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.4.2
> Reporter: Chris Nauroth
> Attachments: ZOOKEEPER-1702.1.patch
>
>
> The problem occurs when a connection attempt is pending and there are
> multiple outbound packets in the queue for other operations. In
> {{ClientCnxnSocketNIO#doIO}}, it is possible to receive notification that the
> socket is writable for the next operation packet before receiving
> notification that the socket is readable for the connection response from the
> server. If the server decides that the session is expired, then it responds
> by immediately closing the socket on its side. If the client has written
> packets after the server has closed its end of the socket, then the TCP stack
> may choose to abort the connection with an RST. When this happens, the
> client doesn't receive an orderly shutdown, and ultimately it fails to
> deliver a session expired event to the application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
