[
https://issues.apache.org/jira/browse/ZOOKEEPER-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271914#comment-13271914
]
Hadoop QA commented on ZOOKEEPER-1444:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12525383/ZOOKEEPER-1444.patch
against trunk revision 1335338.
+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/1066//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1066//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1066//console
This message is automatically generated.
> Idle session-less connections never time out
> --------------------------------------------
>
> Key: ZOOKEEPER-1444
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1444
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.2, 3.4.3, 3.5.0
> Reporter: Jay Shrauner
> Assignee: Jay Shrauner
> Priority: Critical
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1444.patch, ZOOKEEPER-1444.patch
>
>
> A socket connection to the server on which a session is not created will
> never time out. A misbehaving client that opens and leaks connections without
> creating sessions will hold open file descriptors on the server.
> The existing timeout code is implemented at the session level, but the
> servers also should track and expire connections at the connection level.
> Proposed solution is to pull the timeout data structure handling code
> (hashmap of expiry time to sets of objects, simple monotonically incrementing
> nextExpirationTime) from SessionTrackerImpl into its own class in order to
> share it with connection level timeouts to be implemented in
> NIOServerCnxnFactory. Connections can be assigned a small initial timeout
> (proposing something small, like 3s) until a session is created, at which
> point the ServerCnxn session timeout can be used instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
