[
https://issues.apache.org/jira/browse/ZOOKEEPER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964944#comment-13964944
]
Hadoop QA commented on ZOOKEEPER-1346:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12565737/ZOOKEEPER-1346.8.patch
against trunk revision 1586200.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 19 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2032//console
This message is automatically generated.
> Handle 4lws and monitoring on separate port
> -------------------------------------------
>
> Key: ZOOKEEPER-1346
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1346
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Reporter: Camille Fournier
> Assignee: Skye Wanderman-Milne
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-1346.2.patch, ZOOKEEPER-1346.3.patch,
> ZOOKEEPER-1346.4.patch, ZOOKEEPER-1346.6.patch, ZOOKEEPER-1346.7.patch,
> ZOOKEEPER-1346.8.patch, ZOOKEEPER-1346.patch, ZOOKEEPER-1346_jetty.patch
>
>
> Move the 4lws to their own port, off of the client port, and support them
> properly via long-lived sessions instead of polling. Deprecate the 4lw
> support on the client port. Will enable us to enhance the functionality of
> the commands via extended command syntax, address security concerns and fix
> bugs involving the socket close being received before all of the data on the
> client end.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
