Success: ZOOKEEPER- PreCommit Build #439

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/439/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 68.36 MB...]
 [exec] +1 overall.  GitHub Pull Request  Build
 [exec]   
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/439//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/439//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/439//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] e2789a9a0cf03fc96e5b5c92ff77c3c7a2c123c0 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 18 minutes 37 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Could not determine description.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

Success: ZOOKEEPER- PreCommit Build #438

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/438/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 68.63 MB...]
 [exec] +1 overall.  GitHub Pull Request  Build
 [exec]   
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/438//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/438//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/438//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] d934693a2751aa16b294045c81aeee0f95411d46 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 18 minutes 21 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Could not determine description.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

Success: ZOOKEEPER- PreCommit Build #437

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/437/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 67.84 MB...]
 [exec] +1 overall.  GitHub Pull Request  Build
 [exec]   
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/437//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/437//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/437//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] 4a089f896d3171c6e416785a002941824290ff90 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 18 minutes 32 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Could not determine description.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

Failed: ZOOKEEPER- PreCommit Build #436

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/436/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 67.48 MB...]
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] -1 core tests.  The patch failed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/436//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/436//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/436//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] bb78b3b933ef691778f2fff9531666e5d82d8f39 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1642:
 exec returned: 1

Total time: 13 minutes 31 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Compressed 578.70 KB of artifacts by 60.8% relative to #427
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Could not determine description.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  org.apache.zookeeper.test.AsyncHammerTest.testHammer

Error Message:
null

Stack Trace:
junit.framework.AssertionFailedError
at 
org.apache.zookeeper.test.AsyncHammerTest.testHammer(AsyncHammerTest.java:186)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929391#comment-15929391
 ] 

Hadoop QA commented on ZOOKEEPER-2722:
--

-1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 7 new or modified tests.

+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 3.0.1) 
warnings.

-1 release audit.  The applied patch generated 2 release audit warnings 
(more than the trunk's current 0 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-github-pr-build/435//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/435//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/435//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/435//console

This message is automatically generated.

> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER- PreCommit Build #435

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/435/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 68.10 MB...]
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] -1 release audit.  The applied patch generated 2 release audit 
warnings (more than the trunk's current 0 warnings).
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/435//testReport/
 [exec] Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/435//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/435//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/435//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] c4148388beddbf7dbfd6c63ab9464b62b9fa2525 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1641:
 exec returned: 1

Total time: 18 minutes 28 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2722
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

ZooKeeper_branch34_jdk7 - Build # 1445 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1445/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.03 MB...]
[junit] 2017-03-17 02:42:47,849 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-17 02:42:47,849 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-17 02:42:47,850 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-17 02:42:47,850 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-17 02:42:47,850 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-17 02:42:47,851 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-17 02:42:47,852 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-17 02:42:47,853 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-17 02:42:47,853 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-17 02:42:47,853 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-17 02:42:47,854 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test1126540412212901574.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test1126540412212901574.junit.dir/version-2
[junit] 2017-03-17 02:42:47,858 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-17 02:42:47,859 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-17 02:42:47,859 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:38158
[junit] 2017-03-17 02:42:47,860 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:38158
[junit] 2017-03-17 02:42:47,860 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-17 02:42:47,861 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:38158 (no session established for client)
[junit] 2017-03-17 02:42:47,861 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-17 02:42:47,863 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-17 02:42:47,863 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-17 02:42:47,863 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-17 02:42:47,863 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-17 02:42:47,864 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35676
[junit] 2017-03-17 02:42:47,864 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-17 02:42:47,864 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-17 02:42:47,864 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-17 02:42:47,927 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15ada2562f6 closed
[junit] 2017-03-17 02:42:47,927 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-17 02:42:47,928 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15ada2562f6
[junit] 2017-03-17 02:42:47,928 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-17 02:42:47,928 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-17 02:42:47,928 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-17 02:42:47,928 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-17 02:42:47,929 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-17 02:42:47,929 

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929212#comment-15929212
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
I think this does not quite work still 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/434/testReport/junit/org.apache.zookeeper.test/ReadOnlyModeTest/testSessionEstablishment/
 - need more dig see what exactly cause the connection drop.


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
I think this does not quite work still 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/434/testReport/junit/org.apache.zookeeper.test/ReadOnlyModeTest/testSessionEstablishment/
 - need more dig see what exactly cause the connection drop.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Failed: ZOOKEEPER- PreCommit Build #434

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/434/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 67.91 MB...]
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] -1 core tests.  The patch failed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/434//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/434//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/434//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] 5b239c9a3429c0077d73288cc2f8cee19a8e570e logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1642:
 exec returned: 1

Total time: 13 minutes 36 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Compressed 578.71 KB of artifacts by 60.8% relative to #427
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Could not determine description.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

Error Message:
KeeperErrorCode = ConnectionLoss for /test

Stack Trace:
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = 
ConnectionLoss for /test
at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1424)
at 
org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.lang.Thread.run(Thread.java:745)

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929179#comment-15929179
 ] 

Hadoop QA commented on ZOOKEEPER-2722:
--

-1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 7 new or modified tests.

+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 3.0.1) 
warnings.

-1 release audit.  The applied patch generated 2 release audit warnings 
(more than the trunk's current 0 warnings).

-1 core tests.  The patch failed core unit tests.

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/433//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/433//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/433//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/433//console

This message is automatically generated.

> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER- PreCommit Build #433

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/433/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.03 MB...]
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] -1 release audit.  The applied patch generated 2 release audit 
warnings (more than the trunk's current 0 warnings).
 [exec] 
 [exec] -1 core tests.  The patch failed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/433//testReport/
 [exec] Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/433//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/433//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/433//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] 8b6e1aca5c2544b3ec4e75c51bd1d944657d64a2 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1641:
 exec returned: 2

Total time: 21 minutes 21 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2722
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

ZooKeeper_branch34_jdk8 - Build # 922 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/922/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.83 MB...]
[junit] 2017-03-16 23:39:43,137 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-16 23:39:43,137 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-16 23:39:43,138 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-16 23:39:43,138 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-16 23:39:43,138 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-16 23:39:43,138 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-16 23:39:43,139 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 23:39:43,139 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-16 23:39:43,141 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-16 23:39:43,141 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-16 23:39:43,141 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-16 23:39:43,141 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-16 23:39:43,142 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test7216557762692919730.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test7216557762692919730.junit.dir/version-2
[junit] 2017-03-16 23:39:43,145 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 23:39:43,145 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 23:39:43,146 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:45045
[junit] 2017-03-16 23:39:43,146 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:45045
[junit] 2017-03-16 23:39:43,147 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-16 23:39:43,147 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:45045 (no session established for client)
[junit] 2017-03-16 23:39:43,147 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-16 23:39:43,149 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-16 23:39:43,150 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-16 23:39:43,150 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-16 23:39:43,150 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-16 23:39:43,150 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35517
[junit] 2017-03-16 23:39:43,151 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-16 23:39:43,151 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-16 23:39:43,151 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-16 23:39:43,221 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15ad97dc555 closed
[junit] 2017-03-16 23:39:43,221 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-16 23:39:43,221 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15ad97dc555
[junit] 2017-03-16 23:39:43,221 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-16 23:39:43,221 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-16 23:39:43,222 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 23:39:43,222 

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929137#comment-15929137
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
@skamille 
Implementing the idea of waiting for sync connected event to make sure we 
wait until a quorum is formed before prematurely trying a write operation. Made 
some comments in the test case that describes a possible case that client will 
drop connection between connected to r/o server and a quorum reforming. 


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
@skamille 
Implementing the idea of waiting for sync connected event to make sure we 
wait until a quorum is formed before prematurely trying a write operation. Made 
some comments in the test case that describes a possible case that client will 
drop connection between connected to r/o server and a quorum reforming. 


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (ZOOKEEPER-2693) DOS attack on wchp/wchc four letter words (4lw)

[Michael Han (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Han updated ZOOKEEPER-2693:
---
Description: 
The wchp/wchc four letter words can be exploited in a DOS attack on the ZK 
client port - typically 2181. The following POC attack was recently published 
on the web:

https://vulners.com/exploitdb/EDB-ID:41277

The most straightforward way to block this attack is to not allow access to the 
client port to non-trusted clients - i.e. firewall the ZooKeeper service and 
only allow access to trusted applications using it for coordination.

  was:
The wchp/wchc four letter words can be exploited in a DOS attack on the ZK 
client port - typically 2181. The following POC attack was recently published 
on the web:

https://webcache.googleusercontent.com/search?q=cache:_CNGIz10PRYJ:https://www.exploit-db.com/exploits/41277/+=14=en=clnk=us

The most straightforward way to block this attack is to not allow access to the 
client port to non-trusted clients - i.e. firewall the ZooKeeper service and 
only allow access to trusted applications using it for coordination.


> DOS attack on wchp/wchc four letter words (4lw)
> ---
>
> Key: ZOOKEEPER-2693
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2693
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: security, server
>Affects Versions: 3.4.0, 3.5.1, 3.5.2
>Reporter: Patrick Hunt
>Assignee: Michael Han
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2693-01.patch
>
>
> The wchp/wchc four letter words can be exploited in a DOS attack on the ZK 
> client port - typically 2181. The following POC attack was recently published 
> on the web:
> https://vulners.com/exploitdb/EDB-ID:41277
> The most straightforward way to block this attack is to not allow access to 
> the client port to non-trusted clients - i.e. firewall the ZooKeeper service 
> and only allow access to trusted applications using it for coordination.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2693) DOS attack on wchp/wchc four letter words (4lw)

[Michael Han (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929120#comment-15929120
 ] 

Michael Han commented on ZOOKEEPER-2693:


[~breed] https://vulners.com/exploitdb/EDB-ID:41277

> DOS attack on wchp/wchc four letter words (4lw)
> ---
>
> Key: ZOOKEEPER-2693
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2693
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: security, server
>Affects Versions: 3.4.0, 3.5.1, 3.5.2
>Reporter: Patrick Hunt
>Assignee: Michael Han
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2693-01.patch
>
>
> The wchp/wchc four letter words can be exploited in a DOS attack on the ZK 
> client port - typically 2181. The following POC attack was recently published 
> on the web:
> https://webcache.googleusercontent.com/search?q=cache:_CNGIz10PRYJ:https://www.exploit-db.com/exploits/41277/+=14=en=clnk=us
> The most straightforward way to block this attack is to not allow access to 
> the client port to non-trusted clients - i.e. firewall the ZooKeeper service 
> and only allow access to trusted applications using it for coordination.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper_branch35_openjdk7 - Build # 457 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/457/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69.10 MB...]
[junit] 2017-03-16 22:58:48,742 [myid:127.0.0.1:19301] - INFO  
[main-SendThread(127.0.0.1:19301):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19301. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 22:58:48,743 [myid:127.0.0.1:19301] - WARN  
[main-SendThread(127.0.0.1:19301):ClientCnxn$SendThread@1235] - Session 
0x477397f8 for server 127.0.0.1/127.0.0.1:19301, unexpected error, closing 
socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 22:58:49,594 [myid:127.0.0.1:19313] - WARN  
[main-SendThread(127.0.0.1:19313):ClientCnxn$SendThread@1181] - Client session 
timed out, have not heard from server in 30027ms for sessionid 0x40047746cda
[junit] 2017-03-16 22:58:49,594 [myid:127.0.0.1:19313] - INFO  
[main-SendThread(127.0.0.1:19313):ClientCnxn$SendThread@1229] - Client session 
timed out, have not heard from server in 30027ms for sessionid 
0x40047746cda, closing socket connection and attempting reconnect
[junit] 2017-03-16 22:58:49,930 [myid:127.0.0.1:19304] - INFO  
[main-SendThread(127.0.0.1:19304):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19304. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 22:58:49,931 [myid:127.0.0.1:19304] - WARN  
[main-SendThread(127.0.0.1:19304):ClientCnxn$SendThread@1235] - Session 
0x10047739b510001 for server 127.0.0.1/127.0.0.1:19304, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 22:58:50,055 [myid:127.0.0.1:19301] - INFO  
[main-SendThread(127.0.0.1:19301):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19301. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 22:58:50,056 [myid:127.0.0.1:19301] - WARN  
[main-SendThread(127.0.0.1:19301):ClientCnxn$SendThread@1235] - Session 
0x477397f80001 for server 127.0.0.1/127.0.0.1:19301, unexpected error, closing 
socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 22:58:50,261 [myid:127.0.0.1:19304] - INFO  
[main-SendThread(127.0.0.1:19304):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19304. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 22:58:50,262 [myid:127.0.0.1:19304] - WARN  
[main-SendThread(127.0.0.1:19304):ClientCnxn$SendThread@1235] - Session 
0x10047739b51 for server 127.0.0.1/127.0.0.1:19304, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 22:58:50,478 [myid:127.0.0.1:19301] - INFO  
[main-SendThread(127.0.0.1:19301):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19301. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 22:58:50,479 [myid:127.0.0.1:19301] - WARN  
[main-SendThread(127.0.0.1:19301):ClientCnxn$SendThread@1235] - Session 
0x477397f8 for server 127.0.0.1/127.0.0.1:19301, unexpected 

[jira] [Commented] (ZOOKEEPER-2693) DOS attack on wchp/wchc four letter words (4lw)

[Benjamin Reed (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929091#comment-15929091
 ] 

Benjamin Reed commented on ZOOKEEPER-2693:
--

can someone put a good link to the exploit in the description? a cache isn't an 
appropriate link to use.

> DOS attack on wchp/wchc four letter words (4lw)
> ---
>
> Key: ZOOKEEPER-2693
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2693
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: security, server
>Affects Versions: 3.4.0, 3.5.1, 3.5.2
>Reporter: Patrick Hunt
>Assignee: Michael Han
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2693-01.patch
>
>
> The wchp/wchc four letter words can be exploited in a DOS attack on the ZK 
> client port - typically 2181. The following POC attack was recently published 
> on the web:
> https://webcache.googleusercontent.com/search?q=cache:_CNGIz10PRYJ:https://www.exploit-db.com/exploits/41277/+=14=en=clnk=us
> The most straightforward way to block this attack is to not allow access to 
> the client port to non-trusted clients - i.e. firewall the ZooKeeper service 
> and only allow access to trusted applications using it for coordination.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-236) SSL Support for Atomic Broadcast protocol

[Abraham Fine (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929080#comment-15929080
 ] 

Abraham Fine commented on ZOOKEEPER-236:


Hi [~geek101]-

bq. If multiple servers have certs with the same subjectAltName entry of type 
dNSName and that is indeed is how the CA signed them then it should be ok from 
TLS perspective
I agree that at least one of the alt_names needs to match the host from 
configuration (not all of them). 

bq. Take a case where if someone can subvert the CA get signed by it for the 
same domain and subvert DNS then they might as well try few sids starting from 
zero before ZK lets the server connect.
If the CA is subverted (certificates are being issued for servers for domains 
not under their control) and the name service is subverted, hostname 
verification of any kind can't work. Either the CA or the NS (dns or the zk 
config) needs to have integrity. But I think you raise an interesting issue 
where a client can just try multiple id's when connecting to another server 
until it matches the one on its (lets assume stolen) certificate. I did not 
consider that. Let me dig into this a little deeper and see if I can get a 
better idea of what is going on.

bq. We should probably have it off by default and let the admin turn it on.
The latest patch has this behavior.

bq. Also wanted to ask you if we could make the all sockets BufferedSocket by 
default rather then making that conditional on port unification configuration.
Why would we want to do this? I think there is a small performance hit 
involved. 

> SSL Support for Atomic Broadcast protocol
> -
>
> Key: ZOOKEEPER-236
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-236
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: quorum, server
>Reporter: Benjamin Reed
>Assignee: Abraham Fine
>Priority: Minor
>
> We should have the ability to use SSL to authenticate and encrypt the traffic 
> between ZooKeeper servers. For the most part this is a very easy change. We 
> would probably only want to support this for TCP based leader elections.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper-trunk-openjdk7 - Build # 1404 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1404/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 63.39 MB...]
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.close(AbstractNioWorker.java:373)
[junit] at 
org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:81)
[junit] at 
org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:36)
[junit] at 
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779)
[junit] at 
org.jboss.netty.channel.SimpleChannelHandler.closeRequested(SimpleChannelHandler.java:334)
[junit] at 
org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:260)
[junit] at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
[junit] at 
org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
[junit] at org.jboss.netty.channel.Channels.close(Channels.java:812)
[junit] at 
org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:206)
[junit] at 
org.apache.zookeeper.server.NettyServerCnxn.close(NettyServerCnxn.java:112)
[junit] at 
org.apache.zookeeper.server.NettyServerCnxn.sendBuffer(NettyServerCnxn.java:216)
[junit] at 
org.apache.zookeeper.server.NettyServerCnxn.sendCloseSession(NettyServerCnxn.java:455)
[junit] at 
org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:461)
[junit] at 
org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:182)
[junit] at 
org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:113)
[junit] 2017-03-16 22:41:58,522 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x103043fe436 closed
[junit] 2017-03-16 22:41:58,522 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x103043fe436
[junit] 2017-03-16 22:41:58,523 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 227564
[junit] 2017-03-16 22:41:58,523 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 2426
[junit] 2017-03-16 22:41:58,523 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-16 22:41:58,523 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-03-16 22:41:58,523 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-03-16 22:41:58,523 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:22240
[junit] 2017-03-16 22:41:58,527 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-03-16 22:41:58,527 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 22:41:58,527 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-16 22:41:58,528 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-03-16 22:41:58,528 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-16 22:41:58,528 [myid:] - INFO  [ProcessThread(sid:0 
cport:22240)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2017-03-16 22:41:58,528 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-16 22:41:58,528 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-03-16 22:41:58,528 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port22240,name1=InMemoryDataTree]
[junit] 2017-03-16 22:41:58,528 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port22240]
[junit] 2017-03-16 22:41:58,529 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 22240
[junit] 2017-03-16 22:41:58,529 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-03-16 22:41:58,537 [myid:] - INFO  [main:ClientBase@583] - 
fdcount after test is: 7134 at start it was 7134
[junit] 2017-03-16 22:41:58,537 [myid:] - INFO  [main:ZKTestCase$1@68] - 
SUCCEEDED testWatcherAutoResetWithLocal
[junit] 2017-03-16 22:41:58,537 [myid:] - INFO  [main:ZKTestCase$1@63] - 
FINISHED testWatcherAutoResetWithLocal
[junit] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0, 

ZooKeeper_branch34 - Build # 1879 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34/1879/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.47 MB...]
[junit] 2017-03-16 22:30:35,325 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-16 22:30:35,325 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-16 22:30:35,326 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-16 22:30:35,326 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-16 22:30:35,326 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-16 22:30:35,327 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 22:30:35,328 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-16 22:30:35,329 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-16 22:30:35,329 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-16 22:30:35,330 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-16 22:30:35,330 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-16 22:30:35,331 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test5952688302105716729.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test5952688302105716729.junit.dir/version-2
[junit] 2017-03-16 22:30:35,335 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 22:30:35,335 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 22:30:35,336 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:46184
[junit] 2017-03-16 22:30:35,337 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:46184
[junit] 2017-03-16 22:30:35,337 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-16 22:30:35,338 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:46184 (no session established for client)
[junit] 2017-03-16 22:30:35,338 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-16 22:30:35,340 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-16 22:30:35,341 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-16 22:30:35,341 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-16 22:30:35,341 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-16 22:30:35,342 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35682
[junit] 2017-03-16 22:30:35,342 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-16 22:30:35,342 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-16 22:30:35,342 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-16 22:30:35,404 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15ad93e7b9c closed
[junit] 2017-03-16 22:30:35,405 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-16 22:30:35,405 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15ad93e7b9c
[junit] 2017-03-16 22:30:35,405 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-16 22:30:35,406 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-16 22:30:35,406 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 22:30:35,406 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-16 22:30:35,406 [myid:] - INFO  

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928972#comment-15928972
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
I think your idea to create a connector that waits for specific types of 
connection (RO or R/W) is a good idea to try to fix this issue.


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[skamille]

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
I think your idea to create a connector that waits for specific types of 
connection (RO or R/W) is a good idea to try to fix this issue.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

ZooKeeper-trunk-jdk8 - Build # 980 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/980/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 63.83 MB...]
[junit] 2017-03-16 21:47:04,902 [myid:127.0.0.1:16731] - WARN  
[main-SendThread(127.0.0.1:16731):ClientCnxn$SendThread@1235] - Session 
0x10095704fac for server 127.0.0.1/127.0.0.1:16731, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 21:47:05,397 [myid:127.0.0.1:16608] - INFO  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:16608. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 21:47:05,397 [myid:127.0.0.1:16608] - WARN  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1235] - Session 
0x100956cafd1 for server 127.0.0.1/127.0.0.1:16608, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 21:47:05,520 [myid:] - INFO  [ProcessThread(sid:0 
cport:16854)::PrepRequestProcessor@617] - Processed session termination for 
sessionid: 0x10095735ecf
[junit] 2017-03-16 21:47:05,522 [myid:] - INFO  [New I/O worker 
#1829:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port16854,name1=Connections,name2=127.0.0.1,name3=0x10095735ecf]
[junit] 2017-03-16 21:47:05,522 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x10095735ecf
[junit] 2017-03-16 21:47:05,523 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x10095735ecf closed
[junit] 2017-03-16 21:47:05,523 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 114640
[junit] 2017-03-16 21:47:05,523 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 467
[junit] 2017-03-16 21:47:05,523 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-16 21:47:05,523 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-03-16 21:47:05,523 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-03-16 21:47:05,523 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:16854
[junit] 2017-03-16 21:47:05,525 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-03-16 21:47:05,525 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 21:47:05,525 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-16 21:47:05,525 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-03-16 21:47:05,525 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-16 21:47:05,525 [myid:] - INFO  [ProcessThread(sid:0 
cport:16854)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop!
[junit] 2017-03-16 21:47:05,525 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-16 21:47:05,525 [myid:] - INFO  
[main:FinalRequestProcessor@481] - shutdown of request processor complete
[junit] 2017-03-16 21:47:05,525 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port16854,name1=InMemoryDataTree]
[junit] 2017-03-16 21:47:05,525 [myid:] - INFO  [main:MBeanRegistry@128] - 
Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port16854]
[junit] 2017-03-16 21:47:05,526 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 16854
[junit] 2017-03-16 21:47:05,526 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2017-03-16 21:47:05,528 [myid:] - INFO  [main:ClientBase@583] - 
fdcount after test is: 1388 at start it was 1388
[junit] 2017-03-16 21:47:05,528 [myid:] 

ZooKeeper_branch34_openjdk7 - Build # 1431 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1431/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on H22 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch-3.4^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.4^{commit} # timeout=10
Checking out Revision 902bee6410a565aef59ab6b9834fa9e1ead3a742 
(refs/remotes/origin/branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 902bee6410a565aef59ab6b9834fa9e1ead3a742
 > git rev-list 3e5000f5f5b30b838db709fa95228e556612eacf # timeout=10
No emails were triggered.
[ZooKeeper_branch34_openjdk7] $ 
/home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant -Dtest.output=yes 
-Dtest.junit.threads=8 -Dtest.junit.output.format=xml -Djavac.target=1.7 clean 
test-core-java
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

ZooKeeper_branch34_jdk8 - Build # 921 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/921/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.85 MB...]
[junit] 2017-03-16 21:12:09,194 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-16 21:12:09,194 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-16 21:12:09,194 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-16 21:12:09,194 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-16 21:12:09,195 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-16 21:12:09,195 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-16 21:12:09,196 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 21:12:09,196 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-16 21:12:09,198 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-16 21:12:09,198 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-16 21:12:09,198 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-16 21:12:09,199 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-16 21:12:09,199 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test1897723425471006016.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test1897723425471006016.junit.dir/version-2
[junit] 2017-03-16 21:12:09,202 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 21:12:09,202 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 21:12:09,203 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:33024
[junit] 2017-03-16 21:12:09,203 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:33024
[junit] 2017-03-16 21:12:09,204 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-16 21:12:09,204 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:33024 (no session established for client)
[junit] 2017-03-16 21:12:09,204 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-16 21:12:09,207 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-16 21:12:09,207 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-16 21:12:09,207 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-16 21:12:09,208 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-16 21:12:09,208 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35519
[junit] 2017-03-16 21:12:09,209 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-16 21:12:09,209 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-16 21:12:09,209 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-16 21:12:09,276 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15ad8f6ac27 closed
[junit] 2017-03-16 21:12:09,277 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-16 21:12:09,276 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15ad8f6ac27
[junit] 2017-03-16 21:12:09,277 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-16 21:12:09,277 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-16 21:12:09,277 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 21:12:09,278 

ZooKeeper_branch34_jdk7 - Build # 1444 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1444/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.65 MB...]
[junit] 2017-03-16 20:42:27,218 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-16 20:42:27,219 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-16 20:42:27,219 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-16 20:42:27,219 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-16 20:42:27,220 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-16 20:42:27,220 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-16 20:42:27,220 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 20:42:27,221 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-16 20:42:27,222 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-16 20:42:27,223 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-16 20:42:27,223 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-16 20:42:27,223 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-16 20:42:27,224 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test5626733251838754665.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test5626733251838754665.junit.dir/version-2
[junit] 2017-03-16 20:42:27,228 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 20:42:27,229 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 20:42:27,229 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:57059
[junit] 2017-03-16 20:42:27,230 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:57059
[junit] 2017-03-16 20:42:27,230 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-16 20:42:27,231 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:57059 (no session established for client)
[junit] 2017-03-16 20:42:27,231 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-16 20:42:27,233 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-16 20:42:27,234 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-16 20:42:27,234 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-16 20:42:27,234 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-16 20:42:27,235 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35676
[junit] 2017-03-16 20:42:27,235 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-16 20:42:27,235 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-16 20:42:27,235 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-16 20:42:27,300 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15ad8db7b72 closed
[junit] 2017-03-16 20:42:27,301 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-16 20:42:27,301 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15ad8db7b72
[junit] 2017-03-16 20:42:27,301 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-16 20:42:27,301 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-16 20:42:27,301 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 20:42:27,302 

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928828#comment-15928828
 ] 

Hudson commented on ZOOKEEPER-2726:
---

FAILURE: Integrated in Jenkins build ZooKeeper-trunk #3319 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/3319/])
ZOOKEEPER-2726 ZOOKEEPER-2693: Patch for introduces potential race (hanm: rev 
0313a0e0b6c47b316271533165e5830d1ca04478)
* (edit) 
src/java/main/org/apache/zookeeper/server/command/FourLetterCommands.java


> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper-trunk - Build # 3319 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk/3319/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 62.31 MB...]
[junit] Tests run: 103, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
527.664 sec, Thread: 4, Class: org.apache.zookeeper.test.NettyNettySuiteTest
[junit] 2017-03-16 20:29:03,837 [myid:127.0.0.1:19301] - INFO  
[main-SendThread(127.0.0.1:19301):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19301. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 20:29:03,838 [myid:] - INFO  [New I/O boss 
#66:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:19301
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-16 20:29:03,839 [myid:] - WARN  [New I/O boss 
#66:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x2ff0193f] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:19301
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:19301
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-16 20:29:03,839 [myid:] - INFO  [New I/O boss 
#66:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2017-03-16 20:29:03,839 [myid:127.0.0.1:19301] - INFO  
[main-SendThread(127.0.0.1:19301):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x100a57a97be is lost, closing socket connection and attempting 
reconnect

fail.build.on.test.failure:

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1338: The 
following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1219: The 
following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1223: Tests 
failed!

Total time: 12 minutes 54 seconds
Build step 'Execute shell' marked build as failure
[FINDBUGS] Skipping publisher since build result is FAILURE
[WARNINGS] Skipping publisher since build result is FAILURE
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording fingerprints
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[JIRA] Updating issue ZOOKEEPER-2726
[JIRA] Updating issue ZOOKEEPER-2693
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Publishing Javadoc
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: 

[jira] [Commented] (ZOOKEEPER-2693) DOS attack on wchp/wchc four letter words (4lw)

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928829#comment-15928829
 ] 

Hudson commented on ZOOKEEPER-2693:
---

FAILURE: Integrated in Jenkins build ZooKeeper-trunk #3319 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/3319/])
ZOOKEEPER-2726 ZOOKEEPER-2693: Patch for introduces potential race (hanm: rev 
0313a0e0b6c47b316271533165e5830d1ca04478)
* (edit) 
src/java/main/org/apache/zookeeper/server/command/FourLetterCommands.java


> DOS attack on wchp/wchc four letter words (4lw)
> ---
>
> Key: ZOOKEEPER-2693
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2693
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: security, server
>Affects Versions: 3.4.0, 3.5.1, 3.5.2
>Reporter: Patrick Hunt
>Assignee: Michael Han
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2693-01.patch
>
>
> The wchp/wchc four letter words can be exploited in a DOS attack on the ZK 
> client port - typically 2181. The following POC attack was recently published 
> on the web:
> https://webcache.googleusercontent.com/search?q=cache:_CNGIz10PRYJ:https://www.exploit-db.com/exploits/41277/+=14=en=clnk=us
> The most straightforward way to block this attack is to not allow access to 
> the client port to non-trusted clients - i.e. firewall the ZooKeeper service 
> and only allow access to trusted applications using it for coordination.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
I think we support running concurrent JUNIT tests and the number of 
parallel tests is controlled by test.junit.threads - which has default value of 
1 in build.xml. The Jenkins log indicates that this number is 8 on Apache 
Jenkins, though I haven't found where to set it in the job configuration yet. 


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928799#comment-15928799
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
I think we support running concurrent JUNIT tests and the number of 
parallel tests is controlled by test.junit.threads - which has default value of 
1 in build.xml. The Jenkins log indicates that this number is 8 on Apache 
Jenkins, though I haven't found where to set it in the job configuration yet. 


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928770#comment-15928770
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2726:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/197
  
merged, please close the pull request @knusbaum.


> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928768#comment-15928768
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2726:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/198
  
merged, please close the pull request @knusbaum.


> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #197: ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introduces po...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/197
  
merged, please close the pull request @knusbaum.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zookeeper issue #198: ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introduces po...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/198
  
merged, please close the pull request @knusbaum.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Failed: ZOOKEEPER- PreCommit Build #428

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/428/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 34.78 MB...]
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require tests.
 [exec] 
 [exec] -1 javadoc.  The javadoc tool appears to have generated 1 
warning messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] -1 findbugs.  The patch appears to introduce 97 new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] -1 core tests.  The patch failed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/428//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/428//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/428//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] d6051747f4e5434169acbe14df4f794e6548c557 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1714:
 exec returned: 3

Total time: 32 minutes 40 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2726
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.testValidCredentials

Error Message:
waiting for server 0 being up

Stack Trace:
junit.framework.AssertionFailedError: waiting for server 0 being up
at 
org.apache.zookeeper.server.quorum.auth.QuorumAuthTestBase.startQuorum(QuorumAuthTestBase.java:74)
at 
org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.testValidCredentials(QuorumKerberosAuthTest.java:101)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:55)


FAILED:  
org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostBasedAuthTest.testValidCredentials

Error Message:
waiting for server 0 being up

Stack Trace:
junit.framework.AssertionFailedError: waiting for server 0 being up
at 
org.apache.zookeeper.server.quorum.auth.QuorumAuthTestBase.startQuorum(QuorumAuthTestBase.java:74)
at 
org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostBasedAuthTest.testValidCredentials(QuorumKerberosHostBasedAuthTest.java:125)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:55)

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928760#comment-15928760
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Are we running multiple tests in parallel on Jenkins? I think the logs 
support this thesis but they seem to have many different tests logging into the 
same lines as the testSessionEstablishment test and I'm terrible confused by 
how that is happening.


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[skamille]

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Are we running multiple tests in parallel on Jenkins? I think the logs 
support this thesis but they seem to have many different tests logging into the 
same lines as the testSessionEstablishment test and I'm terrible confused by 
how that is happening.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[Michael Han (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Han resolved ZOOKEEPER-2726.

   Resolution: Fixed
Fix Version/s: 3.5.3
   3.4.10
   3.6.0

Issue resolved by pull request 198
[https://github.com/apache/zookeeper/pull/198]

> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
> Fix For: 3.6.0, 3.4.10, 3.5.3
>
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER- PreCommit Build #432

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/432/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2.04 KB...]
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H7(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
at com.sun.proxy.$Proxy80.checkoutBranch(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:324)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:995)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1102)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 
origin/trunk" returned status code 1:
stdout: 
stderr: error: pathspec 'origin/trunk' did not match any file(s) known to git.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:64)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2060)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:81)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:894)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:869)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Putting comment on the pull request
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: ZOOKEEPER- PreCommit Build #431

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/431/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 75.49 KB...]
warning: Cannot merge binary files: docs/zookeeperAdmin.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)
warning: Cannot merge binary files: docs/recipes.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)
warning: Cannot merge binary files: docs/linkmap.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)
warning: Cannot merge binary files: docs/javaExample.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)
warning: Cannot merge binary files: docs/index.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)
warning: Cannot merge binary files: docs/bookkeeperStream.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)
warning: Cannot merge binary files: docs/bookkeeperStarted.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)
warning: Cannot merge binary files: docs/bookkeeperProgrammer.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)
warning: Cannot merge binary files: docs/bookkeeperOverview.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)
warning: Cannot merge binary files: docs/bookkeeperConfig.pdf (HEAD vs. 
902bee6410a565aef59ab6b9834fa9e1ead3a742)

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1766)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1762)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1409)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$3.execute(CliGitAPIImpl.java:588)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.merge(AbstractGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.merge(CliGitAPIImpl.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:894)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:869)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H5(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
at com.sun.proxy.$Proxy80.merge(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.merge(RemoteGitImpl.java:435)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:107)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:995)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1102)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Putting comment on the pull request
Email was triggered for: Failure - Any
Sending email 

Failed: ZOOKEEPER- PreCommit Build #430

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/430/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2.04 KB...]
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H7(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
at com.sun.proxy.$Proxy80.checkoutBranch(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:324)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:995)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1102)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 
origin/trunk" returned status code 1:
stdout: 
stderr: error: pathspec 'origin/trunk' did not match any file(s) known to git.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:64)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2060)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:81)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:894)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:869)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Putting comment on the pull request
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928755#comment-15928755
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2726:
---

Github user asfgit closed the pull request at:

https://github.com/apache/zookeeper/pull/196


> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper pull request #196: ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introd...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zookeeper/pull/196


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2693) DOS attack on wchp/wchc four letter words (4lw)

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928735#comment-15928735
 ] 

Hadoop QA commented on ZOOKEEPER-2693:
--

-1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+0 tests included.  The patch appears to be a documentation patch that 
doesn't require tests.

+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 3.0.1) 
warnings.

-1 release audit.  The applied patch generated 2 release audit warnings 
(more than the trunk's current 0 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-github-pr-build/429//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/429//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/429//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/429//console

This message is automatically generated.

> DOS attack on wchp/wchc four letter words (4lw)
> ---
>
> Key: ZOOKEEPER-2693
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2693
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: security, server
>Affects Versions: 3.4.0, 3.5.1, 3.5.2
>Reporter: Patrick Hunt
>Assignee: Michael Han
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2693-01.patch
>
>
> The wchp/wchc four letter words can be exploited in a DOS attack on the ZK 
> client port - typically 2181. The following POC attack was recently published 
> on the web:
> https://webcache.googleusercontent.com/search?q=cache:_CNGIz10PRYJ:https://www.exploit-db.com/exploits/41277/+=14=en=clnk=us
> The most straightforward way to block this attack is to not allow access to 
> the client port to non-trusted clients - i.e. firewall the ZooKeeper service 
> and only allow access to trusted applications using it for coordination.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[Michael Han (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928736#comment-15928736
 ] 

Michael Han commented on ZOOKEEPER-2726:


lgtm, thanks for the patch [~knusbaum].

[~fpj] or [~phunt]: please help add [~knusbaum] to jira contributor list, 
thanks in advance.

> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Failed: ZOOKEEPER- PreCommit Build #429

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/429/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 68.07 MB...]
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] -1 release audit.  The applied patch generated 2 release audit 
warnings (more than the trunk's current 0 warnings).
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/429//testReport/
 [exec] Release audit warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/429//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/429//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/429//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] 8f40ca58feab2db4a94bcf4567ee29ffaa4635b5 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1641:
 exec returned: 1

Total time: 20 minutes 49 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2726
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

ZooKeeper_branch35_openjdk7 - Build # 456 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/456/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 66.70 MB...]
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:16707
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-16 19:51:21,855 [myid:] - INFO  [New I/O boss 
#2493:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2017-03-16 19:51:21,855 [myid:127.0.0.1:16707] - INFO  
[main-SendThread(127.0.0.1:16707):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x20046d08fd4 is lost, closing socket connection and attempting 
reconnect
[junit] 2017-03-16 19:51:21,978 [myid:127.0.0.1:16608] - INFO  
[main-SendThread(127.0.0.1:16608):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:16608. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 19:51:21,979 [myid:] - INFO  [New I/O boss 
#18:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:16608
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-16 19:51:21,979 [myid:] - WARN  [New I/O boss 
#18:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x4b58c8c5] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:16608
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:16608
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-16 19:51:21,979 

[jira] [Commented] (ZOOKEEPER-2693) DOS attack on wchp/wchc four letter words (4lw)

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928716#comment-15928716
 ] 

Hadoop QA commented on ZOOKEEPER-2693:
--

+1 overall.  GitHub Pull Request  Build
  

+1 @author.  The patch does not contain any @author tags.

+0 tests included.  The patch appears to be a documentation patch that 
doesn't require tests.

+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 3.0.1) 
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-github-pr-build/427//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/427//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/427//console

This message is automatically generated.

> DOS attack on wchp/wchc four letter words (4lw)
> ---
>
> Key: ZOOKEEPER-2693
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2693
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: security, server
>Affects Versions: 3.4.0, 3.5.1, 3.5.2
>Reporter: Patrick Hunt
>Assignee: Michael Han
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2693-01.patch
>
>
> The wchp/wchc four letter words can be exploited in a DOS attack on the ZK 
> client port - typically 2181. The following POC attack was recently published 
> on the web:
> https://webcache.googleusercontent.com/search?q=cache:_CNGIz10PRYJ:https://www.exploit-db.com/exploits/41277/+=14=en=clnk=us
> The most straightforward way to block this attack is to not allow access to 
> the client port to non-trusted clients - i.e. firewall the ZooKeeper service 
> and only allow access to trusted applications using it for coordination.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2460) Remove javacc dependency from public Maven pom

[Enrico Olivelli (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928717#comment-15928717
 ] 

Enrico Olivelli commented on ZOOKEEPER-2460:


Thank you Mohammad

> Remove javacc dependency from public Maven pom
> --
>
> Key: ZOOKEEPER-2460
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2460
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.5.2
>Reporter: Enrico Olivelli
>Priority: Critical
> Fix For: 3.5.3, 3.6.0
>
>
> during the vote of 3.5.2-ALPHA RC 0 we found a Maven dependency to javacc in 
> published pom for zookeeper
> {code}
> 
> net.java.dev.javacc
> javacc
> 5.0compile
> 
> {code}
> this dependency appears not to be useful and should be removed
> this was the tested pom: 
> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.2-alpha/zookeeper-3.5.2-alpha.pom



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Success: ZOOKEEPER- PreCommit Build #427

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/427/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 68.86 MB...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +0 tests included.  The patch appears to be a documentation 
patch that doesn't require tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 3.0.1) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/427//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/427//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/427//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] 94c9a201ab3b2399300584ad4752859581e7a344 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 18 minutes 45 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2726
Putting comment on the pull request
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928699#comment-15928699
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2726:
---

GitHub user knusbaum opened a pull request:

https://github.com/apache/zookeeper/pull/198

ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introduces potential race condition

#196 

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

$ git pull https://github.com/knusbaum/zookeeper ZOOKEEPER-2726-3.5

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

https://github.com/apache/zookeeper/pull/198.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 #198


commit b26e34ca00d28a165a17af535f1fb00668c1680c
Author: Kyle Nusbaum 
Date:   2017-03-16T19:31:03Z

Synchronizing 4lw methods




> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper pull request #198: ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introd...

[knusbaum]

GitHub user knusbaum opened a pull request:

https://github.com/apache/zookeeper/pull/198

ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introduces potential race condition

#196 

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

$ git pull https://github.com/knusbaum/zookeeper ZOOKEEPER-2726-3.5

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

https://github.com/apache/zookeeper/pull/198.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 #198


commit b26e34ca00d28a165a17af535f1fb00668c1680c
Author: Kyle Nusbaum 
Date:   2017-03-16T19:31:03Z

Synchronizing 4lw methods




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928698#comment-15928698
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2726:
---

GitHub user knusbaum opened a pull request:

https://github.com/apache/zookeeper/pull/197

ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introduces potential race condition

#196 

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

$ git pull https://github.com/knusbaum/zookeeper ZOOKEEPER-2726-3.4

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

https://github.com/apache/zookeeper/pull/197.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 #197


commit 39e66833c6efaa1a25aaac97aa523deea4853f08
Author: Kyle Nusbaum 
Date:   2017-03-16T19:06:46Z

Synchronizing 4-letter-word methods




> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper pull request #197: ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introd...

[knusbaum]

GitHub user knusbaum opened a pull request:

https://github.com/apache/zookeeper/pull/197

ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introduces potential race condition

#196 

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

$ git pull https://github.com/knusbaum/zookeeper ZOOKEEPER-2726-3.4

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

https://github.com/apache/zookeeper/pull/197.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 #197


commit 39e66833c6efaa1a25aaac97aa523deea4853f08
Author: Kyle Nusbaum 
Date:   2017-03-16T19:06:46Z

Synchronizing 4-letter-word methods




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928688#comment-15928688
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2726:
---

GitHub user knusbaum opened a pull request:

https://github.com/apache/zookeeper/pull/196

ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introduces potential race condition

Synchronizing these methods prevents potential race conditions.

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

$ git pull https://github.com/knusbaum/zookeeper ZOOKEEPER-2726-master

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

https://github.com/apache/zookeeper/pull/196.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 #196


commit 3c79d303aaaf105e129580b7d9fe450944f4173b
Author: Kyle Nusbaum 
Date:   2017-03-16T19:22:45Z

Synchronizing 4lw methods




> Patch for ZOOKEEPER-2693 introduces potential race condition
> 
>
> Key: ZOOKEEPER-2726
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
>
> We noticed when porting the patch, that isEnabled is not thread-safe. 
> Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper pull request #196: ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introd...

[knusbaum]

GitHub user knusbaum opened a pull request:

https://github.com/apache/zookeeper/pull/196

ZOOKEEPER-2726: Patch for ZOOKEEPER-2693 introduces potential race condition

Synchronizing these methods prevents potential race conditions.

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

$ git pull https://github.com/knusbaum/zookeeper ZOOKEEPER-2726-master

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

https://github.com/apache/zookeeper/pull/196.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 #196


commit 3c79d303aaaf105e129580b7d9fe450944f4173b
Author: Kyle Nusbaum 
Date:   2017-03-16T19:22:45Z

Synchronizing 4lw methods




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928682#comment-15928682
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Let me also check the Apache Jenkins logs on the failed cases see what 
happened there.


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Let me also check the Apache Jenkins logs on the failed cases see what 
happened there.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928678#comment-15928678
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
That's a good one, it sounds possible. We can force the watcher only wait 
for SyncConnected event (rather than both SyncConnectedEvent and 
ConnectedReadyOnly event), so we will guarantee the client connected to a RW 
server before executing the write operation.


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
That's a good one, it sounds possible. We can force the watcher only wait 
for SyncConnected event (rather than both SyncConnectedEvent and 
ConnectedReadyOnly event), so we will guarantee the client connected to a RW 
server before executing the write operation.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZOOKEEPER-2726) Patch for ZOOKEEPER-2693 introduces potential race condition

[Kyle Nusbaum (JIRA)]

Kyle Nusbaum created ZOOKEEPER-2726:
---

 Summary: Patch for ZOOKEEPER-2693 introduces potential race 
condition
 Key: ZOOKEEPER-2726
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2726
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Kyle Nusbaum


We noticed when porting the patch, that isEnabled is not thread-safe. 
Synchronizing it and resetWhitelist should solve the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper-trunk-jdk8 - Build # 979 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/979/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 63.87 MB...]
[junit] 2017-03-16 19:14:24,927 [myid:127.0.0.1:24813] - WARN  
[main-SendThread(127.0.0.1:24813):ClientCnxn$SendThread@1235] - Session 
0x2041e56b7d0 for server 127.0.0.1/127.0.0.1:24813, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 19:14:24,991 [myid:127.0.0.1:24810] - INFO  
[main-SendThread(127.0.0.1:24810):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24810. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 19:14:24,991 [myid:127.0.0.1:24810] - WARN  
[main-SendThread(127.0.0.1:24810):ClientCnxn$SendThread@1235] - Session 
0x1041e56b772 for server 127.0.0.1/127.0.0.1:24810, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 19:14:25,120 [myid:127.0.0.1:24687] - INFO  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:24687. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 19:14:25,121 [myid:127.0.0.1:24687] - WARN  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1235] - Session 
0x1041e52aac8 for server 127.0.0.1/127.0.0.1:24687, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 19:14:25,651 [myid:] - INFO  [ProcessThread(sid:0 
cport:24933)::PrepRequestProcessor@617] - Processed session termination for 
sessionid: 0x1041e59fb9f
[junit] 2017-03-16 19:14:25,653 [myid:] - INFO  
[SyncThread:0:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port24933,name1=Connections,name2=127.0.0.1,name3=0x1041e59fb9f]
[junit] 2017-03-16 19:14:25,653 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x1041e59fb9f closed
[junit] 2017-03-16 19:14:25,653 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 68331
[junit] 2017-03-16 19:14:25,653 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 468
[junit] 2017-03-16 19:14:25,654 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testWatcherAutoResetWithLocal
[junit] 2017-03-16 19:14:25,653 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1041e59fb9f
[junit] 2017-03-16 19:14:25,654 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-03-16 19:14:25,654 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-03-16 19:14:25,654 [myid:] - INFO  
[main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:24933
[junit] 2017-03-16 19:14:25,655 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-03-16 19:14:25,655 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 19:14:25,655 [myid:] - INFO  
[main:SessionTrackerImpl@232] - Shutting down
[junit] 2017-03-16 19:14:25,655 [myid:] - INFO  
[main:PrepRequestProcessor@1008] - Shutting down
[junit] 2017-03-16 19:14:25,655 [myid:] - INFO  
[main:SyncRequestProcessor@191] - Shutting down
[junit] 2017-03-16 19:14:25,655 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited!
[junit] 2017-03-16 19:14:25,656 [myid:] - INFO  

[jira] [Commented] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database

[Michael Han (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928606#comment-15928606
 ] 

Michael Han commented on ZOOKEEPER-2712:


[~rakeshr] Yes it is sad that we still need 1.6 support otherwise this is not 
an issue. 

Since you mentioned that these tests (with ZOOKEEPER-2689) pass consistently on 
your windows, could this be a JDK / OS issue? Otherwise if the test itself is 
flaky then I would imagine windows test will fail sometimes. 

> MiniKdc test case intermittently failing due to principal not found in 
> Kerberos database
> 
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.11
>
> Attachments: 
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the 
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR 
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client 
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos 
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos 
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN  
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos 
> database (6)
> {code}
> Will attach the detailed log to jira.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928612#comment-15928612
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Is it possible that what happens is the client connects again in read-only 
mode, and then is bumped when quorum happens to be achieved? It seems like that 
shouldn't happen but it seems like the one race condition that I can somewhat 
imagine.


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[skamille]

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Is it possible that what happens is the client connects again in read-only 
mode, and then is bumped when quorum happens to be achieved? It seems like that 
shouldn't happen but it seems like the one race condition that I can somewhat 
imagine.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: github merging?

[Edward Ribeiro]

Hi, it looks like an error on setuptools:
http://stackoverflow.com/questions/41827464/pythong-pycparser-setup-error
 (the lib is different but the error is the same on lines)

Eddie

On Thu, Mar 16, 2017 at 1:58 PM, Camille Fournier 
wrote:

> Thanks Michael I'll check and see if upgrading to 2.7.11 fixes it
>
> On Thu, Mar 16, 2017 at 12:26 PM, Michael Han  wrote:
>
> > Looks like a python environment issue. What python version and
> installation
> > are you using? I am using python 2.7.11 installed via homebrew for
> > reference. Also make sure pip is installed (sudo easy_install pip).
> >
> > On Thu, Mar 16, 2017 at 8:48 AM, Camille Fournier 
> > wrote:
> >
> > > Also, can we get this in the 3.5 branch as well?
> > >
> > > On Thu, Mar 16, 2017 at 11:03 AM, Camille Fournier  >
> > > wrote:
> > >
> > > > I'm trying to follow the instructions on the wiki to approve changes:
> > > > https://cwiki.apache.org/confluence/display/ZOOKEEPER/
> > > > Merging+Github+Pull+Requests
> > > >
> > > > but it does not appear to work. Specifically, this merge script:
> > > > python zk-merge-pr.py
> > > >
> > > > is erroring out with:
> > > >
> > > >   File "/Library/Python/2.7/site-packages/pbr-2.0.0-py2.7.egg/
> > > pbr/version.py",
> > > > line 25, in 
> > > >
> > > > import pkg_resources
> > > >
> > > >   File "build/bdist.macosx-10.12-intel/egg/pkg_resources/__
> init__.py",
> > > > line 72, in 
> > > >
> > > >   File "build/bdist.macosx-10.12-intel/egg/packaging/
> requirements.py",
> > > > line 59, in 
> > > >
> > > > TypeError: __call__() takes exactly 2 arguments (1 given)
> > > >
> > > >
> > > > Any ideas?
> > > >
> > > >
> > > > C
> > > >
> > >
> >
> >
> >
> > --
> > Cheers
> > Michael.
> >
>

[jira] [Commented] (ZOOKEEPER-2460) Remove javacc dependency from public Maven pom

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928601#comment-15928601
 ] 

Hudson commented on ZOOKEEPER-2460:
---

FAILURE: Integrated in Jenkins build ZooKeeper-trunk #3318 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/3318/])
ZOOKEEPER-2460 Remove javacc dependency from public Maven pom (arshad: rev 
b4dded46f901fbc2128c7f752107a1391d676968)
* (delete) src/java/lib/javacc.LICENSE.txt
* (edit) ivy.xml
* (edit) build.xml


> Remove javacc dependency from public Maven pom
> --
>
> Key: ZOOKEEPER-2460
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2460
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.5.2
>Reporter: Enrico Olivelli
>Priority: Critical
> Fix For: 3.5.3, 3.6.0
>
>
> during the vote of 3.5.2-ALPHA RC 0 we found a Maven dependency to javacc in 
> published pom for zookeeper
> {code}
> 
> net.java.dev.javacc
> javacc
> 5.0compile
> 
> {code}
> this dependency appears not to be useful and should be removed
> this was the tested pom: 
> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.2-alpha/zookeeper-3.5.2-alpha.pom



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

ZooKeeper-trunk - Build # 3318 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk/3318/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 70.81 MB...]
[junit] 2017-03-16 18:29:53,034 [myid:127.0.0.1:19430] - INFO  
[main-SendThread(127.0.0.1:19430):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x300a511f53e is lost, closing socket connection and attempting 
reconnect
[junit] 2017-03-16 18:29:53,035 [myid:127.0.0.1:19391] - INFO  
[main-SendThread(127.0.0.1:19391):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:19391. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 18:29:53,035 [myid:] - INFO  [New I/O boss 
#8778:ClientCnxnSocketNetty$1@127] - future isn't success, cause: {}
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:19391
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-16 18:29:53,035 [myid:] - WARN  [New I/O boss 
#8778:ClientCnxnSocketNetty$ZKClientHandler@439] - Exception caught: [id: 
0x66b2a15e] EXCEPTION: java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:19391
[junit] java.net.ConnectException: Connection refused: 
127.0.0.1/127.0.0.1:19391
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:152)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)
[junit] at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
[junit] at 
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
[junit] at 
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
[junit] at 
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
[junit] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[junit] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[junit] at java.lang.Thread.run(Thread.java:745)
[junit] 2017-03-16 18:29:53,035 [myid:] - INFO  [New I/O boss 
#8778:ClientCnxnSocketNetty@208] - channel is told closing
[junit] 2017-03-16 18:29:53,036 [myid:127.0.0.1:19391] - INFO  
[main-SendThread(127.0.0.1:19391):ClientCnxn$SendThread@1231] - channel for 
sessionid 0x600a50f82360001 is lost, closing socket connection and attempting 
reconnect
[junit] Test org.apache.zookeeper.test.NettyNettySuiteTest FAILED

fail.build.on.test.failure:

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1338: The 
following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1219: The 
following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/build.xml:1223: Tests 
failed!

Total time: 13 minutes 31 seconds
Build step 'Execute shell' marked build as failure
[FINDBUGS] Skipping publisher since build result is FAILURE
[WARNINGS] Skipping publisher since build result is FAILURE
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording fingerprints
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[JIRA] Updating issue ZOOKEEPER-2460
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Publishing Javadoc
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting 

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
@skamille Interesting, curious to see what you find out. 


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928587#comment-15928587
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
@skamille Interesting, curious to see what you find out. 


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2460) Remove javacc dependency from public Maven pom

[Mohammad Arshad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928584#comment-15928584
 ] 

Mohammad Arshad commented on ZOOKEEPER-2460:


Merged to master: 
https://github.com/apache/zookeeper/commit/b4dded46f901fbc2128c7f752107a1391d676968
Merged to branch-3.5: 
https://github.com/apache/zookeeper/commit/f5aacfcdfd09be337f1e60d20fc86e95958d2b0d
Thanks [~eolivelli] for your contribution.

[~fpj], can you please add [~eolivelli] in contributors list and assign the 
issue to him.

> Remove javacc dependency from public Maven pom
> --
>
> Key: ZOOKEEPER-2460
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2460
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.5.2
>Reporter: Enrico Olivelli
>Priority: Critical
> Fix For: 3.5.3, 3.6.0
>
>
> during the vote of 3.5.2-ALPHA RC 0 we found a Maven dependency to javacc in 
> published pom for zookeeper
> {code}
> 
> net.java.dev.javacc
> javacc
> 5.0compile
> 
> {code}
> this dependency appears not to be useful and should be removed
> this was the tested pom: 
> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.2-alpha/zookeeper-3.5.2-alpha.pom



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[skamille]

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
FWIW I can repro this on my desktop so let me see if I can figure out 
what's happening


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928583#comment-15928583
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
FWIW I can repro this on my desktop so let me see if I can figure out 
what's happening


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928570#comment-15928570
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
> ConnectionLossException can happen after a connection between ZooKeeper 
client and server has been established, right? So having the check only in 
watcher is not enough. A pass in watcher does not guarantee 
ConnectionLossException will not occur in a later point in time. Imagine an 
extreme case where the a network partition happened between client / server 
after a session establishment - the client will first get a connected event, 
and watcher happily reports everything is fine, then subsequent operation (e.g. 
create) will fail with ConnectionLossException until the network healed.

Right but we're talking about a test case. If we have the issue that our 
tests can connect to ZK, then randomly drop connections while in the midst of 
the testing, that feels like a problem we should figure out. It should not 
happen, and we rely on this particular "watch till connection then proceed with 
test" functionality in tests throughout the code base. The fact that it is only 
failing here seems to me a stranger problem. I'm supportive of adding more 
logging to see if we can debug it.


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[skamille]

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
> ConnectionLossException can happen after a connection between ZooKeeper 
client and server has been established, right? So having the check only in 
watcher is not enough. A pass in watcher does not guarantee 
ConnectionLossException will not occur in a later point in time. Imagine an 
extreme case where the a network partition happened between client / server 
after a session establishment - the client will first get a connected event, 
and watcher happily reports everything is fine, then subsequent operation (e.g. 
create) will fail with ConnectionLossException until the network healed.

Right but we're talking about a test case. If we have the issue that our 
tests can connect to ZK, then randomly drop connections while in the midst of 
the testing, that feels like a problem we should figure out. It should not 
happen, and we rely on this particular "watch till connection then proceed with 
test" functionality in tests throughout the code base. The fact that it is only 
failing here seems to me a stranger problem. I'm supportive of adding more 
logging to see if we can debug it.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928556#comment-15928556
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
>> if that creation is failing due to connection loss, shouldn't the places 
that check the watcher connection fail there instead of in your check?

ConnectionLossException can happen *after* a connection between ZooKeeper 
client and server has been established, right? So having the check only in 
watcher is not enough. A pass in watcher does not guarantee 
ConnectionLossException will not occur in a later point in time. Imagine an 
extreme case where the a network partition happened between client / server 
after a session establishment - the client will first get a connected event, 
and watcher happily reports everything is fine, then subsequent operation (e.g. 
create) will fail with ConnectionLossException until the network healed. 

>> I think it's worth understanding why we are getting a connection event 
in the watcher that should be waiting for connection, but still failing by not 
connecting, instead of fixing this with additional waiting.

Yes I'd like to know what causes this though I had a hard time to reproduce 
this failure locally / in internal Jenkins. It is so far only reproducible in 
Apache Jenkins. I can add some loggings to capture more contexts when the 
failure happens on Apache Jenkins, but in that case the retry logic in create 
is still needed, unless we can prove it is not possible to get a 
ConnectionLossException after a session establishment.



> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (ZOOKEEPER-2460) Remove javacc dependency from public Maven pom

[Mohammad Arshad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mohammad Arshad resolved ZOOKEEPER-2460.

   Resolution: Fixed
Fix Version/s: 3.5.3
   3.6.0

Issue resolved by pull request 116
[https://github.com/apache/zookeeper/pull/116]

> Remove javacc dependency from public Maven pom
> --
>
> Key: ZOOKEEPER-2460
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2460
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.5.2
>Reporter: Enrico Olivelli
>Priority: Critical
> Fix For: 3.6.0, 3.5.3
>
>
> during the vote of 3.5.2-ALPHA RC 0 we found a Maven dependency to javacc in 
> published pom for zookeeper
> {code}
> 
> net.java.dev.javacc
> javacc
> 5.0compile
> 
> {code}
> this dependency appears not to be useful and should be removed
> this was the tested pom: 
> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.2-alpha/zookeeper-3.5.2-alpha.pom



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
>> if that creation is failing due to connection loss, shouldn't the places 
that check the watcher connection fail there instead of in your check?

ConnectionLossException can happen *after* a connection between ZooKeeper 
client and server has been established, right? So having the check only in 
watcher is not enough. A pass in watcher does not guarantee 
ConnectionLossException will not occur in a later point in time. Imagine an 
extreme case where the a network partition happened between client / server 
after a session establishment - the client will first get a connected event, 
and watcher happily reports everything is fine, then subsequent operation (e.g. 
create) will fail with ConnectionLossException until the network healed. 

>> I think it's worth understanding why we are getting a connection event 
in the watcher that should be waiting for connection, but still failing by not 
connecting, instead of fixing this with additional waiting.

Yes I'd like to know what causes this though I had a hard time to reproduce 
this failure locally / in internal Jenkins. It is so far only reproducible in 
Apache Jenkins. I can add some loggings to capture more contexts when the 
failure happens on Apache Jenkins, but in that case the retry logic in create 
is still needed, unless we can prove it is not possible to get a 
ConnectionLossException after a session establishment.



---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Failed: ZOOKEEPER- PreCommit Build #426

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/426/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2.04 KB...]
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H6(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
at com.sun.proxy.$Proxy80.checkoutBranch(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:324)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:995)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1102)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 
origin/trunk" returned status code 1:
stdout: 
stderr: error: pathspec 'origin/trunk' did not match any file(s) known to git.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:64)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2060)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:81)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:894)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:869)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:828)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Archiving artifacts
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files 
were found. Configuration error?
[description-setter] Could not determine description.
Putting comment on the pull request
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (ZOOKEEPER-2460) Remove javacc dependency from public Maven pom

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928553#comment-15928553
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2460:
---

Github user asfgit closed the pull request at:

https://github.com/apache/zookeeper/pull/116


> Remove javacc dependency from public Maven pom
> --
>
> Key: ZOOKEEPER-2460
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2460
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.5.2
>Reporter: Enrico Olivelli
>Priority: Critical
>
> during the vote of 3.5.2-ALPHA RC 0 we found a Maven dependency to javacc in 
> published pom for zookeeper
> {code}
> 
> net.java.dev.javacc
> javacc
> 5.0compile
> 
> {code}
> this dependency appears not to be useful and should be removed
> this was the tested pom: 
> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.2-alpha/zookeeper-3.5.2-alpha.pom



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper pull request #116: ZOOKEEPER-2460 Remove javacc dependency from pu...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zookeeper/pull/116


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2460) Remove javacc dependency from public Maven pom

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928534#comment-15928534
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2460:
---

Github user arshadmohammad commented on the issue:

https://github.com/apache/zookeeper/pull/116
  
LGTM, +1


> Remove javacc dependency from public Maven pom
> --
>
> Key: ZOOKEEPER-2460
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2460
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.5.2
>Reporter: Enrico Olivelli
>Priority: Critical
>
> during the vote of 3.5.2-ALPHA RC 0 we found a Maven dependency to javacc in 
> published pom for zookeeper
> {code}
> 
> net.java.dev.javacc
> javacc
> 5.0compile
> 
> {code}
> this dependency appears not to be useful and should be removed
> this was the tested pom: 
> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.2-alpha/zookeeper-3.5.2-alpha.pom



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #116: ZOOKEEPER-2460 Remove javacc dependency from public Ma...

[arshadmohammad]

Github user arshadmohammad commented on the issue:

https://github.com/apache/zookeeper/pull/116
  
LGTM, +1


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: github merging?

[Camille Fournier]

Thanks Michael I'll check and see if upgrading to 2.7.11 fixes it

On Thu, Mar 16, 2017 at 12:26 PM, Michael Han  wrote:

> Looks like a python environment issue. What python version and installation
> are you using? I am using python 2.7.11 installed via homebrew for
> reference. Also make sure pip is installed (sudo easy_install pip).
>
> On Thu, Mar 16, 2017 at 8:48 AM, Camille Fournier 
> wrote:
>
> > Also, can we get this in the 3.5 branch as well?
> >
> > On Thu, Mar 16, 2017 at 11:03 AM, Camille Fournier 
> > wrote:
> >
> > > I'm trying to follow the instructions on the wiki to approve changes:
> > > https://cwiki.apache.org/confluence/display/ZOOKEEPER/
> > > Merging+Github+Pull+Requests
> > >
> > > but it does not appear to work. Specifically, this merge script:
> > > python zk-merge-pr.py
> > >
> > > is erroring out with:
> > >
> > >   File "/Library/Python/2.7/site-packages/pbr-2.0.0-py2.7.egg/
> > pbr/version.py",
> > > line 25, in 
> > >
> > > import pkg_resources
> > >
> > >   File "build/bdist.macosx-10.12-intel/egg/pkg_resources/__init__.py",
> > > line 72, in 
> > >
> > >   File "build/bdist.macosx-10.12-intel/egg/packaging/requirements.py",
> > > line 59, in 
> > >
> > > TypeError: __call__() takes exactly 2 arguments (1 given)
> > >
> > >
> > > Any ideas?
> > >
> > >
> > > C
> > >
> >
>
>
>
> --
> Cheers
> Michael.
>

Re: github merging?

[Michael Han]

Looks like a python environment issue. What python version and installation
are you using? I am using python 2.7.11 installed via homebrew for
reference. Also make sure pip is installed (sudo easy_install pip).

On Thu, Mar 16, 2017 at 8:48 AM, Camille Fournier 
wrote:

> Also, can we get this in the 3.5 branch as well?
>
> On Thu, Mar 16, 2017 at 11:03 AM, Camille Fournier 
> wrote:
>
> > I'm trying to follow the instructions on the wiki to approve changes:
> > https://cwiki.apache.org/confluence/display/ZOOKEEPER/
> > Merging+Github+Pull+Requests
> >
> > but it does not appear to work. Specifically, this merge script:
> > python zk-merge-pr.py
> >
> > is erroring out with:
> >
> >   File "/Library/Python/2.7/site-packages/pbr-2.0.0-py2.7.egg/
> pbr/version.py",
> > line 25, in 
> >
> > import pkg_resources
> >
> >   File "build/bdist.macosx-10.12-intel/egg/pkg_resources/__init__.py",
> > line 72, in 
> >
> >   File "build/bdist.macosx-10.12-intel/egg/packaging/requirements.py",
> > line 59, in 
> >
> > TypeError: __call__() takes exactly 2 arguments (1 given)
> >
> >
> > Any ideas?
> >
> >
> > C
> >
>



-- 
Cheers
Michael.

Re: github merging?

[Camille Fournier]

Also, can we get this in the 3.5 branch as well?

On Thu, Mar 16, 2017 at 11:03 AM, Camille Fournier 
wrote:

> I'm trying to follow the instructions on the wiki to approve changes:
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/
> Merging+Github+Pull+Requests
>
> but it does not appear to work. Specifically, this merge script:
> python zk-merge-pr.py
>
> is erroring out with:
>
>   File "/Library/Python/2.7/site-packages/pbr-2.0.0-py2.7.egg/pbr/version.py",
> line 25, in 
>
> import pkg_resources
>
>   File "build/bdist.macosx-10.12-intel/egg/pkg_resources/__init__.py",
> line 72, in 
>
>   File "build/bdist.macosx-10.12-intel/egg/packaging/requirements.py",
> line 59, in 
>
> TypeError: __call__() takes exactly 2 arguments (1 given)
>
>
> Any ideas?
>
>
> C
>

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928260#comment-15928260
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Basically, I think it's worth understanding why we are getting a connection 
event in the watcher that should be waiting for connection, but still failing 
by not connecting, instead of fixing this with additional waiting.


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[skamille]

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Basically, I think it's worth understanding why we are getting a connection 
event in the watcher that should be waiting for connection, but still failing 
by not connecting, instead of fixing this with additional waiting.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2722) Flaky Test: org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928238#comment-15928238
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2722:
---

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Right but my point is, if that creation is failing due to connection loss, 
shouldn't the places that check the watcher connection fail there instead of in 
your check? The first place you added the retries there is no watcher 
connection check, the rest of them there already is, and my understanding is 
that the watcher should not get past that check if the connection isn't 
established.


> Flaky Test: 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment
> ---
>
> Key: ZOOKEEPER-2722
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2722
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-build, flaky-test
> Fix For: 3.5.3, 3.6.0
>
>
> {noformat}
> Error Message
> KeeperErrorCode = ConnectionLoss for /test
> Stacktrace
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode 
> = ConnectionLoss for /test
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
>   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
>   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1423)
>   at 
> org.apache.zookeeper.test.ReadOnlyModeTest.testSessionEstablishment(ReadOnlyModeTest.java:238)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Looks like we should retry before giving up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #191: ZOOKEEPER-2722: fix flaky testSessionEstablishment tes...

[skamille]

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/191
  
Right but my point is, if that creation is failing due to connection loss, 
shouldn't the places that check the watcher connection fail there instead of in 
your check? The first place you added the retries there is no watcher 
connection check, the rest of them there already is, and my understanding is 
that the watcher should not get past that check if the connection isn't 
established.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

github merging?

[Camille Fournier]

I'm trying to follow the instructions on the wiki to approve changes:
https://cwiki.apache.org/confluence/display/ZOOKEEPER/Merging+Github+Pull+Requests

but it does not appear to work. Specifically, this merge script:
python zk-merge-pr.py

is erroring out with:

  File
"/Library/Python/2.7/site-packages/pbr-2.0.0-py2.7.egg/pbr/version.py",
line 25, in 

import pkg_resources

  File "build/bdist.macosx-10.12-intel/egg/pkg_resources/__init__.py", line
72, in 

  File "build/bdist.macosx-10.12-intel/egg/packaging/requirements.py", line
59, in 

TypeError: __call__() takes exactly 2 arguments (1 given)


Any ideas?


C

[jira] [Commented] (ZOOKEEPER-2724) Skip cert files for releaseaudit target.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928214#comment-15928214
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2724:
---

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/194
  
The lack of this appears to be breaking builds so this looks good to me. I 
will commit.


> Skip cert files for releaseaudit target.
> 
>
> Key: ZOOKEEPER-2724
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2724
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>Priority: Blocker
>  Labels: build
> Fix For: 3.5.3
>
>
> In branch-3.5 release auditing generating warnings against cert files as 
> these files don't contain Apache License (AL) header. I don't think these 
> files should be checked because they are not source files, and we skip them 
> in master branch. We should do the same for branch-3.5 by skipping these cert 
> files as well. This should be fixed before 3.5.3 release.
> Attach the snippet of warning for reference:
> {noformat}
> [rat:report]  !? 
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build/zookeeper-3.5.3-alpha-SNAPSHOT/contrib/rest/conf/keys/rest.cer
> [rat:report]  !? 
> /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build/zookeeper-3.5.3-alpha-SNAPSHOT/src/contrib/rest/conf/keys/rest.cer
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zookeeper issue #194: ZOOKEEPER-2724: Skip cert files for releaseaudit targe...

[skamille]

Github user skamille commented on the issue:

https://github.com/apache/zookeeper/pull/194
  
The lack of this appears to be breaking builds so this looks good to me. I 
will commit.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

ZooKeeper_branch34_openjdk7 - Build # 1430 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1430/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H15 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git fetch --tags --progress git://git.apache.org/zookeeper.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch-3.4^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.4^{commit} # timeout=10
Checking out Revision 3e5000f5f5b30b838db709fa95228e556612eacf 
(refs/remotes/origin/branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3e5000f5f5b30b838db709fa95228e556612eacf
 > git rev-list 3e5000f5f5b30b838db709fa95228e556612eacf # timeout=10
No emails were triggered.
[ZooKeeper_branch34_openjdk7] $ 
/home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant -Dtest.output=yes 
-Dtest.junit.threads=8 -Dtest.junit.output.format=xml -Djavac.target=1.7 clean 
test-core-java
Error: JAVA_HOME is not defined correctly.
  We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
No tests ran.

ZooKeeper_branch34_jdk8 - Build # 920 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/920/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.46 MB...]
[junit] 2017-03-16 14:17:56,674 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-16 14:17:56,674 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-16 14:17:56,674 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-16 14:17:56,674 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-16 14:17:56,674 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-16 14:17:56,675 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-16 14:17:56,675 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 14:17:56,676 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-16 14:17:56,678 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-16 14:17:56,678 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-16 14:17:56,678 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-16 14:17:56,678 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-16 14:17:56,678 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test5616230935108743096.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test5616230935108743096.junit.dir/version-2
[junit] 2017-03-16 14:17:56,682 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 14:17:56,682 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 14:17:56,683 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:41770
[junit] 2017-03-16 14:17:56,683 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:41770
[junit] 2017-03-16 14:17:56,684 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-16 14:17:56,684 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:41770 (no session established for client)
[junit] 2017-03-16 14:17:56,684 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-16 14:17:56,686 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-16 14:17:56,686 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-16 14:17:56,687 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-16 14:17:56,687 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-16 14:17:56,687 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35519
[junit] 2017-03-16 14:17:56,687 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-16 14:17:56,687 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-16 14:17:56,688 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-16 14:17:56,757 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15ad77b7417 closed
[junit] 2017-03-16 14:17:56,757 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15ad77b7417
[junit] 2017-03-16 14:17:56,757 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-16 14:17:56,758 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-16 14:17:56,758 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-16 14:17:56,758 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 14:17:56,758 

ZooKeeper_branch34_jdk7 - Build # 1443 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1443/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 31.03 MB...]
[junit] 2017-03-16 13:48:54,607 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-03-16 13:48:54,607 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-03-16 13:48:54,608 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-03-16 13:48:54,608 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-03-16 13:48:54,608 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-03-16 13:48:54,608 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-03-16 13:48:54,609 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 13:48:54,609 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-03-16 13:48:54,610 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-03-16 13:48:54,611 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-03-16 13:48:54,611 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-03-16 13:48:54,611 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-03-16 13:48:54,612 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test5358923593271645986.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test5358923593271645986.junit.dir/version-2
[junit] 2017-03-16 13:48:54,615 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 13:48:54,616 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-03-16 13:48:54,616 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:36799
[junit] 2017-03-16 13:48:54,617 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing 
stat command from /127.0.0.1:36799
[junit] 2017-03-16 13:48:54,617 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-03-16 13:48:54,617 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1044] - Closed socket connection for client 
/127.0.0.1:36799 (no session established for client)
[junit] 2017-03-16 13:48:54,618 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-03-16 13:48:54,619 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-03-16 13:48:54,620 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-03-16 13:48:54,620 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-03-16 13:48:54,620 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-03-16 13:48:54,620 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35676
[junit] 2017-03-16 13:48:54,621 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-03-16 13:48:54,621 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-03-16 13:48:54,621 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-03-16 13:48:54,693 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15ad760df30 closed
[junit] 2017-03-16 13:48:54,693 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-03-16 13:48:54,693 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15ad760df30
[junit] 2017-03-16 13:48:54,694 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-03-16 13:48:54,694 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-03-16 13:48:54,694 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2017-03-16 13:48:54,694 

ZooKeeper_branch35_openjdk7 - Build # 455 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/455/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 66.66 MB...]
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 13:20:10,809 [myid:127.0.0.1:30272] - INFO  
[main-SendThread(127.0.0.1:30272):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30272. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 13:20:10,810 [myid:127.0.0.1:30272] - WARN  
[main-SendThread(127.0.0.1:30272):ClientCnxn$SendThread@1235] - Session 
0x700456da33b for server 127.0.0.1/127.0.0.1:30272, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 13:20:10,838 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop!
[junit] 2017-03-16 13:20:10,910 [myid:127.0.0.1:30178] - INFO  
[main-SendThread(127.0.0.1:30178):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30178. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 13:20:10,911 [myid:127.0.0.1:30178] - WARN  
[main-SendThread(127.0.0.1:30178):ClientCnxn$SendThread@1235] - Session 
0x1004569c2390003 for server 127.0.0.1/127.0.0.1:30178, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 13:20:10,922 [myid:127.0.0.1:30073] - INFO  
[main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30073. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 13:20:10,922 [myid:127.0.0.1:30073] - WARN  
[main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1235] - Session 
0x10045676e6f for server 127.0.0.1/127.0.0.1:30073, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 13:20:10,986 [myid:127.0.0.1:30272] - INFO  
[main-SendThread(127.0.0.1:30272):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30272. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 13:20:10,987 [myid:127.0.0.1:30272] - WARN  
[main-SendThread(127.0.0.1:30272):ClientCnxn$SendThread@1235] - Session 
0x700456da33b0001 for server 127.0.0.1/127.0.0.1:30272, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-03-16 13:20:11,090 [myid:127.0.0.1:30175] - INFO  
[main-SendThread(127.0.0.1:30175):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:30175. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2017-03-16 13:20:11,091 [myid:127.0.0.1:30175] - WARN  
[main-SendThread(127.0.0.1:30175):ClientCnxn$SendThread@1235] - Session 
0x3004569c244 for server 127.0.0.1/127.0.0.1:30175, unexpected error, 
closing socket connection and attempting reconnect
[junit]