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

2017-02-14 Thread Michael Han (JIRA)

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

Michael Han commented on ZOOKEEPER-2693:


The compatibility argument makes most of sense - so how about this:

* For both 3.5/3.4, provide a new configuration option that allow admin of 
ensemble to white list 4lw commands exposed to the world.
* If such an option is not provided in zoo.cfg ZK will choose a list of default 
commands in white list. Otherwise what's put in zoo.cfg will overwrite default 
values.

I think this is a good scoping that balances addressing this specific issue and 
ease of implementation.

Rate limiter and deprecating 4lw in favor of AdminServer (for 3.5) can be done 
as separate issues later (after 3.4.10 / 3.5.3 released). 

> 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
>
>
> 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-2693) DOS attack on wchp/wchc four letter words (4lw)

2017-02-14 Thread Patrick Hunt (JIRA)

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

Patrick Hunt commented on ZOOKEEPER-2693:
-

bq. The configuration option of disabling 4lw or a subset of it seems an 
ultimate escape hatch

yes, this was my thought as well. 

Your argument around having the rate limiter makes sense, that's one of the 
things I was thinking about this morning when I originally recommended it. Now 
I'm also leaning toward the "whitelist" approach because I think it's a very 
clean solution to the problem. What I mean is no on/off config, just a single 
configuration listing the whitelisted 4lw. If the list is empty it's off (the 
map is empty), otw the user can select the commands they would like to expose. 

If we implement something for 3.4 the same b/w compat argument should hold. 
i.e. if we do rate limiting in 3.4 we should also have the same functionality 
in 3.5.

> 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
>
>
> 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-2693) DOS attack on wchp/wchc four letter words (4lw)

2017-02-14 Thread Patrick Hunt (JIRA)

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

Patrick Hunt commented on ZOOKEEPER-2693:
-

bq. Do you think we still need provide a middle ground for 4lws for 3.5 release 
/ master branch instead of completely shut it off?

Here's another way to think about this: we provide b/w compat when moving from 
X.Y.Z to X.Y+1.# As such we can deprecate 4lw in 3.5 (even turn it off by 
default), but we can't remove it entirely. If we want to provide a fix for this 
issue, and still maintain b/w compat in 3.5 then we should make it 
configurable. Does that make sense?

> 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
>
>
> 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] [Comment Edited] (ZOOKEEPER-2693) DOS attack on wchp/wchc four letter words (4lw)

2017-02-14 Thread Michael Han (JIRA)

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

Michael Han edited comment on ZOOKEEPER-2693 at 2/15/17 4:44 AM:
-

bq. I don't think we can go with an all/nothing approach, many users would 
still want to be able to monitor their system using existing 4lw based infra.
[~phunt] The current patch is for branch 3.5, where we have AdminServer, which 
is designed to replace four letter words. That is why the patch provides only 
an option to completely disable the entire four letter words instead of only 
disabling a specific subset. The AdminServer will make four letter words 
irrelevant and because AdminServer does not share the ZooKeeper client port 
(which sometimes have to be exposed publicly), admin of ensemble protected 
AdminServer port with firewall without interrupting ZooKeeper clients. Besides, 
this seems a good opportunity to push for deprecating four letter words in 
favor of AdminServer which is around for quite a while given the security 
concerns. 

Do you think we still need provide a middle ground for 4lws for 3.5 release / 
master branch instead of completely shut it off? 


was (Author: hanm):
bq. I don't think we can go with an all/nothing approach, many users would 
still want to be able to monitor their system using existing 4lw based infra.
[~phunt] The current patch is for branch 3.5, where we have AdminServer, which 
is designed to replace four letter words. That is why the patch provides only 
an option to completely disable the entire four letter words instead of only 
disabling a specific subset. The AdminServer will make four letter words 
irrelevant and because AdminServer does not share the ZooKeeper client port 
(which sometimes have to be exposed publicly), admin of ensemble protected 
AdminServer port with firewall without interrupting ZooKeeper clients. Besides, 
this seems a good opportunity to push for deprecating four letter words in 
favor of AdminServer which is around for quite a while given the security 
concerns. 

Do you think we still need four letter words turn on by default for the coming 
3.5 release / master branch?

> 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
>
>
> 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-2693) DOS attack on wchp/wchc four letter words (4lw)

2017-02-14 Thread Michael Han (JIRA)

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

Michael Han commented on ZOOKEEPER-2693:


As for patch for branch-3.4, I am thinking instead of disabling a subset of 
commands, we could just add a rate limiter. All commands will still be 
available to use (including the wchp/wchc ones), but they are rate limited not 
to cause any damages. Disabling a sub set of commands does not solve the root 
issue, and I imagine it might still be possible to do DOS on servers acceptor 
threads by just utilizing white listed four letter words at massive scale on 
client side. 

The configuration option of disabling 4lw or a subset of it seems an ultimate 
escape hatch - I guess it does not hurt to provide both as option for users, 
but for branch-3.4 it looks like rate limiter is a must have to address current 
and potential issues when the server client port is accessible from public.

> 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
>
>
> 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-2693) DOS attack on wchp/wchc four letter words (4lw)

2017-02-14 Thread Michael Han (JIRA)

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

Michael Han commented on ZOOKEEPER-2693:


bq. I don't think we can go with an all/nothing approach, many users would 
still want to be able to monitor their system using existing 4lw based infra.
[~phunt] The current patch is for branch 3.5, where we have AdminServer, which 
is designed to replace four letter words. That is why the patch provides only 
an option to completely disable the entire four letter words instead of only 
disabling a specific subset. The AdminServer will make four letter words 
irrelevant and because AdminServer does not share the ZooKeeper client port 
(which sometimes have to be exposed publicly), admin of ensemble protected 
AdminServer port with firewall without interrupting ZooKeeper clients. Besides, 
this seems a good opportunity to push for deprecating four letter words in 
favor of AdminServer which is around for quite a while given the security 
concerns. 

Do you think we still need four letter words turn on by default for the coming 
3.5 release / master branch?

> 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
>
>
> 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_branch34_jdk7 - Build # 1407 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1407/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 239770 lines...]
[junit] 2017-02-15 02:41:55,810 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-02-15 02:41:55,810 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-02-15 02:41:55,810 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-02-15 02:41:55,811 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-02-15 02:41:55,811 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-02-15 02:41:55,811 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-02-15 02:41:55,811 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-15 02:41:55,812 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-02-15 02:41:55,813 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-02-15 02:41:55,814 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-02-15 02:41:55,814 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-02-15 02:41:55,814 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-02-15 02:41:55,814 [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/test7053325362153123348.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test7053325362153123348.junit.dir/version-2
[junit] 2017-02-15 02:41:55,818 [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-02-15 02:41:55,818 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-15 02:41:55,819 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:44765
[junit] 2017-02-15 02:41:55,819 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@838] - Processing 
stat command from /127.0.0.1:44765
[junit] 2017-02-15 02:41:55,820 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-02-15 02:41:55,820 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1019] - Closed socket connection for client 
/127.0.0.1:44765 (no session established for client)
[junit] 2017-02-15 02:41:55,820 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-02-15 02:41:55,823 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-02-15 02:41:55,823 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-02-15 02:41:55,823 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-02-15 02:41:55,823 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-02-15 02:41:55,824 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35674
[junit] 2017-02-15 02:41:55,824 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-02-15 02:41:55,824 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-02-15 02:41:55,824 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-02-15 02:41:55,895 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15a3fa5cfd7 closed
[junit] 2017-02-15 02:41:55,896 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-02-15 02:41:55,896 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15a3fa5cfd7
[junit] 2017-02-15 02:41:55,896 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-02-15 02:41:55,896 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-02-15 02:41:55,897 [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-02-15 

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

2017-02-14 Thread Patrick Hunt (JIRA)

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

Patrick Hunt commented on ZOOKEEPER-2693:
-

I looked at the patch. It is reasonable, but I don't think we can go with an 
all/nothing approach, many users would still want to be able to monitor their 
system using existing 4lw based infra, while mitigating the attack, and this 
doesn't allow any middle ground. 

How about on/off as you have in the current patch, but also allow a list of 
"whitelisted" 4lw - the default could be "ruok" and "srvr" or something of that 
nature. Notice we are building the list today here FourLetterCommands, and 
could build a list containing the configured whitelist instead? What do you 
think.

> 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
>
>
> 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-2693) DOS attack on wchp/wchc four letter words (4lw)

2017-02-14 Thread Patrick Hunt (JIRA)

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

Patrick Hunt commented on ZOOKEEPER-2693:
-

Yes, effectively a rate limiter. However I was thinking in terms of number of 
4lw that we would allow to run concurrently, vs number of operations per 
second. This would address outliers - possibly very long running 4lw. "only let 
one 4lw run at a time, even it if takes 20 seconds".

Historically we've limited our dependency on other components. Neither 3.4 nor 
3.5 are pulling in guava today. One of the issues we've heard from users is 
that (component versioning issues in particular) complicates deployment. I 
think adding new dependencies to something like 3.4.10, ostensibly a fix 
release, would be unwise.

I threw the idea out there as a suggestion. We can take it or leave it for the 
various releases.

> 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
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3
>
>
> 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] [Assigned] (ZOOKEEPER-2693) DOS attack on wchp/wchc four letter words (4lw)

2017-02-14 Thread Patrick Hunt (JIRA)

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

Patrick Hunt reassigned ZOOKEEPER-2693:
---

Assignee: Michael Han

> 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
>
>
> 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-2693) DOS attack on wchp/wchc four letter words (4lw)

2017-02-14 Thread Michael Han (JIRA)

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

Michael Han commented on ZOOKEEPER-2693:


[~phunt] I think what you are talking to is to add rate limiting to 4lw / admin 
server. There are various schemes and trade offs for rate limiter 
implementation, and I'd prefer using a well tested one like the rate limiter 
from Guava if we are ok to pull in it as a dependency. 

> 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
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3
>
>
> 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)


Failed: ZOOKEEPER- PreCommit Build #324

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/324/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 11 lines...]
Fetching upstream changes from git://github.com/apache/zookeeper.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > git://github.com/apache/zookeeper.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 15e3f7fccc770783786e8097f7a6618509bfee0f 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 15e3f7fccc770783786e8097f7a6618509bfee0f
 > git rev-list cd0e323831c8b4cde64976325bfc79bb53cdd9b7 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson4011598405376952871.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files 
were found. Configuration error?
[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) 
##
No tests ran.

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

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

GitHub user hanm opened a pull request:

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

ZOOKEEPER-2693: DOS attack on wchp/wchc four letter words (4lw)

This is for master / branch-3.5:

* Introduce a new configuration option that by default turn off 4lw.
* Update docs that explicitly states ZooKeeper should not be deployed open 
to world for access and deprecating 4lw in favor of Jetty.

With these combined, the attack described in ZOOKEEPER-2693 is not possible 
if ZooKeeper is put behind a firewall where Jetty AdminServer is not publicly 
accessible.

Note for tests: I did not add any unit tests to test 4lw disabling because 
it is fairly obvious (though I have to update a place to prevent existing test 
broken, because we are using 4lw extensively to query test server states. We 
could query AdminServer instead but I consider that's a future work item - and 
even if we use AdminServer exclusively we can't dump 4lw completely because 
AdminServer test depends on 4lw - chicken egg problem.). 


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

$ git pull https://github.com/hanm/zookeeper ZOOKEEPER-2693

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

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


commit b70e19ecdcd8f78bb8ac2d380a07968cbb683b3b
Author: Michael Han 
Date:   2017-02-14T22:24:05Z

Initial commit that turns four letter words off by default for 3.5.x branch.
Pending test cases and doc changes.

commit 7f3420573774a23dafc8fcbbe3873392d0c9090a
Author: Michael Han 
Date:   2017-02-14T22:41:01Z

Update Admin Doc source for 4lw changes.

commit b808940d5aed3c707b50df417a558123df4a03cd
Author: Michael Han 
Date:   2017-02-15T00:02:35Z

Update doc with security guideline.

commit f296225793dcf7bc289b63b2ff9ca7d30291fb69
Author: Michael Han 
Date:   2017-02-15T00:06:07Z

Fix broken tests.




> 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
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3
>
>
> 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)


Failed: ZOOKEEPER- PreCommit Build #323

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/323/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 34 lines...]
 > git rev-parse refs/tags/changes/323^{commit} # timeout=10
 > git merge f296225793dcf7bc289b63b2ff9ca7d30291fb69 # timeout=10
 > git rev-parse master^{commit} # timeout=10
Checking out Revision f296225793dcf7bc289b63b2ff9ca7d30291fb69 (master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f f296225793dcf7bc289b63b2ff9ca7d30291fb69
 > git rev-parse origin/master^{commit} # timeout=10
 > git rev-list 15e3f7fccc770783786e8097f7a6618509bfee0f # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson6973583140506597377.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386178
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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
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
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) 
##
No tests ran.

[GitHub] zookeeper pull request #179: ZOOKEEPER-2693: DOS attack on wchp/wchc four le...

2017-02-14 Thread hanm
GitHub user hanm opened a pull request:

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

ZOOKEEPER-2693: DOS attack on wchp/wchc four letter words (4lw)

This is for master / branch-3.5:

* Introduce a new configuration option that by default turn off 4lw.
* Update docs that explicitly states ZooKeeper should not be deployed open 
to world for access and deprecating 4lw in favor of Jetty.

With these combined, the attack described in ZOOKEEPER-2693 is not possible 
if ZooKeeper is put behind a firewall where Jetty AdminServer is not publicly 
accessible.

Note for tests: I did not add any unit tests to test 4lw disabling because 
it is fairly obvious (though I have to update a place to prevent existing test 
broken, because we are using 4lw extensively to query test server states. We 
could query AdminServer instead but I consider that's a future work item - and 
even if we use AdminServer exclusively we can't dump 4lw completely because 
AdminServer test depends on 4lw - chicken egg problem.). 


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

$ git pull https://github.com/hanm/zookeeper ZOOKEEPER-2693

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

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


commit b70e19ecdcd8f78bb8ac2d380a07968cbb683b3b
Author: Michael Han 
Date:   2017-02-14T22:24:05Z

Initial commit that turns four letter words off by default for 3.5.x branch.
Pending test cases and doc changes.

commit 7f3420573774a23dafc8fcbbe3873392d0c9090a
Author: Michael Han 
Date:   2017-02-14T22:41:01Z

Update Admin Doc source for 4lw changes.

commit b808940d5aed3c707b50df417a558123df4a03cd
Author: Michael Han 
Date:   2017-02-15T00:02:35Z

Update doc with security guideline.

commit f296225793dcf7bc289b63b2ff9ca7d30291fb69
Author: Michael Han 
Date:   2017-02-15T00:06:07Z

Fix broken tests.




---
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 #322

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/322/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 33 lines...]
 > git rev-parse refs/tags/changes/322^{commit} # timeout=10
 > git merge bfc180b2fe5a5b31298c39b12b3b668fff780927 # timeout=10
 > git rev-parse branch-3.4^{commit} # timeout=10
Checking out Revision bfc180b2fe5a5b31298c39b12b3b668fff780927 (branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f bfc180b2fe5a5b31298c39b12b3b668fff780927
 > git rev-parse origin/branch-3.4^{commit} # timeout=10
 > git rev-list 2de93fe450b909ff76ac8bd8fa44296a515845a5 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson6586261991852366613.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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
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
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) 
##
No tests ran.

[jira] [Commented] (ZOOKEEPER-2696) Eclipse ant ask no longer determines correct classpath for tests after ZOOKEEPER-2689

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/178
  
Hoping you can take a look @rakeshadr 


> Eclipse ant ask no longer determines correct classpath for tests after 
> ZOOKEEPER-2689
> -
>
> Key: ZOOKEEPER-2696
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2696
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.10
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> Following the changes made in ZOOKEEPER-2689 IDE's using the .classpath file 
> generated by the eclipse ant task (I tested both idea and eclipse) cannot 
> compile the tests.



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


[GitHub] zookeeper issue #178: ZOOKEEPER-2696: Eclipse ant ask no longer determines c...

2017-02-14 Thread afine
Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/178
  
Hoping you can take a look @rakeshadr 


---
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 #321

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/321/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 33 lines...]
 > git rev-parse refs/tags/changes/321^{commit} # timeout=10
 > git merge 0baa88c7fe48a09624298a6240ab1e3cef3527e9 # timeout=10
 > git rev-parse branch-3.4^{commit} # timeout=10
Checking out Revision 0baa88c7fe48a09624298a6240ab1e3cef3527e9 (branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0baa88c7fe48a09624298a6240ab1e3cef3527e9
 > git rev-parse origin/branch-3.4^{commit} # timeout=10
 > git rev-list 2de93fe450b909ff76ac8bd8fa44296a515845a5 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson7971264236175093298.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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
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
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) 
##
No tests ran.

Failed: ZOOKEEPER- PreCommit Build #320

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/320/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 33 lines...]
 > git rev-parse refs/tags/changes/320^{commit} # timeout=10
 > git merge 431ea33a0708b16b0f7216d0f106c34fbda141be # timeout=10
 > git rev-parse branch-3.4^{commit} # timeout=10
Checking out Revision 431ea33a0708b16b0f7216d0f106c34fbda141be (branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 431ea33a0708b16b0f7216d0f106c34fbda141be
 > git rev-parse origin/branch-3.4^{commit} # timeout=10
 > git rev-list 2de93fe450b909ff76ac8bd8fa44296a515845a5 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson1825053720581051489.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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
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
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) 
##
No tests ran.

Failed: ZOOKEEPER- PreCommit Build #319

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/319/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 33 lines...]
 > git rev-parse refs/tags/changes/319^{commit} # timeout=10
 > git merge 9e01f595595616d41751f13b3b704c4a2f8b1ed2 # timeout=10
 > git rev-parse branch-3.4^{commit} # timeout=10
Checking out Revision 9e01f595595616d41751f13b3b704c4a2f8b1ed2 (branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 9e01f595595616d41751f13b3b704c4a2f8b1ed2
 > git rev-parse origin/branch-3.4^{commit} # timeout=10
 > git rev-list 2de93fe450b909ff76ac8bd8fa44296a515845a5 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson4386127418245426235.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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
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
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) 
##
No tests ran.

[jira] [Commented] (ZOOKEEPER-2696) Eclipse ant ask no longer determines correct classpath for tests after ZOOKEEPER-2689

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

GitHub user afine opened a pull request:

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

ZOOKEEPER-2696: Eclipse ant ask no longer determines correct classpath for 
tests after ZOOKEEPER-2689

After pulling branch-3.4 i noticed that I could no longer compile and run 
the tests within my IDE. 

The .classpath file generated by the eclipse ant task was missing necessary 
dependencies. These missing dependencies all appear to be transitive from 
dependencies brought in by ZOOKEEPER-2689 (which is why ant is able to run the 
tests). There were two possible ways to fix this, this patch explicitly lists 
the new transitive dependencies that are required by our test code. Another 
solution would be to remove `transitive="false"` from `` in the eclipse target 
of our `build.xml`. This solution would introduce even more transitive 
dependencies to the .classpath.

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

$ git pull https://github.com/afine/zookeeper ZOOKEEPER-2696

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

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


commit bc8d6c35594f24fbb7ebf13066a746f5b7246cd1
Author: Abraham Fine 
Date:   2017-02-15T00:03:35Z

ZOOKEEPER-2696: Eclipse ant ask no longer determines correct classpath 
after ZOOKEEPER-2689




> Eclipse ant ask no longer determines correct classpath for tests after 
> ZOOKEEPER-2689
> -
>
> Key: ZOOKEEPER-2696
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2696
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.10
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> Following the changes made in ZOOKEEPER-2689 IDE's using the .classpath file 
> generated by the eclipse ant task (I tested both idea and eclipse) cannot 
> compile the tests.



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


Failed: ZOOKEEPER- PreCommit Build #318

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/318/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 33 lines...]
 > git rev-parse refs/tags/changes/318^{commit} # timeout=10
 > git merge bc8d6c35594f24fbb7ebf13066a746f5b7246cd1 # timeout=10
 > git rev-parse branch-3.4^{commit} # timeout=10
Checking out Revision bc8d6c35594f24fbb7ebf13066a746f5b7246cd1 (branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f bc8d6c35594f24fbb7ebf13066a746f5b7246cd1
 > git rev-parse origin/branch-3.4^{commit} # timeout=10
 > git rev-list 2de93fe450b909ff76ac8bd8fa44296a515845a5 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson8067135324865645831.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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
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
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) 
##
No tests ran.

[GitHub] zookeeper pull request #178: ZOOKEEPER-2696: Eclipse ant ask no longer deter...

2017-02-14 Thread afine
GitHub user afine opened a pull request:

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

ZOOKEEPER-2696: Eclipse ant ask no longer determines correct classpath for 
tests after ZOOKEEPER-2689

After pulling branch-3.4 i noticed that I could no longer compile and run 
the tests within my IDE. 

The .classpath file generated by the eclipse ant task was missing necessary 
dependencies. These missing dependencies all appear to be transitive from 
dependencies brought in by ZOOKEEPER-2689 (which is why ant is able to run the 
tests). There were two possible ways to fix this, this patch explicitly lists 
the new transitive dependencies that are required by our test code. Another 
solution would be to remove `transitive="false"` from `` in the eclipse target 
of our `build.xml`. This solution would introduce even more transitive 
dependencies to the .classpath.

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

$ git pull https://github.com/afine/zookeeper ZOOKEEPER-2696

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

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


commit bc8d6c35594f24fbb7ebf13066a746f5b7246cd1
Author: Abraham Fine 
Date:   2017-02-15T00:03:35Z

ZOOKEEPER-2696: Eclipse ant ask no longer determines correct classpath 
after ZOOKEEPER-2689




---
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-2696) Eclipse ant ask no longer determines correct classpath for tests after ZOOKEEPER-2689

2017-02-14 Thread Abraham Fine (JIRA)

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

Abraham Fine updated ZOOKEEPER-2696:

Affects Version/s: 3.4.10

> Eclipse ant ask no longer determines correct classpath for tests after 
> ZOOKEEPER-2689
> -
>
> Key: ZOOKEEPER-2696
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2696
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.10
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> Following the changes made in ZOOKEEPER-2689 IDE's using the .classpath file 
> generated by the eclipse ant task (I tested both idea and eclipse) cannot 
> compile the tests.



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


[jira] [Updated] (ZOOKEEPER-2696) Eclipse ant ask no longer determines correct classpath for tests after ZOOKEEPER-2689

2017-02-14 Thread Abraham Fine (JIRA)

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

Abraham Fine updated ZOOKEEPER-2696:

Summary: Eclipse ant ask no longer determines correct classpath for tests 
after ZOOKEEPER-2689  (was: Eclipse ant ask no longer determines correct 
classpath after ZOOKEEPER-2689)

> Eclipse ant ask no longer determines correct classpath for tests after 
> ZOOKEEPER-2689
> -
>
> Key: ZOOKEEPER-2696
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2696
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>
> Following the changes made in ZOOKEEPER-2689 IDE's using the .classpath file 
> generated by the eclipse ant task (I tested both idea and eclipse) cannot 
> compile the tests.



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


[jira] [Created] (ZOOKEEPER-2696) Eclipse ant ask no longer determines correct classpath after ZOOKEEPER-2689

2017-02-14 Thread Abraham Fine (JIRA)
Abraham Fine created ZOOKEEPER-2696:
---

 Summary: Eclipse ant ask no longer determines correct classpath 
after ZOOKEEPER-2689
 Key: ZOOKEEPER-2696
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2696
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Abraham Fine
Assignee: Abraham Fine


Following the changes made in ZOOKEEPER-2689 IDE's using the .classpath file 
generated by the eclipse ant task (I tested both idea and eclipse) cannot 
compile the tests.



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


ZooKeeper_branch34 - Build # 1837 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34/1837/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 58 lines...]
  collisions:0 txqueuelen:0 
  RX bytes:2374970464268 (2.3 TB)  TX bytes:2374970464268 (2.3 TB)

core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
6
/home/jenkins/tools/ant/latest/bin/ant clean
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
mv: cannot stat ‘build/*.tar.gz’: No such file or directory
mv: cannot stat ‘build/*.jar’: No such file or directory
mv: cannot stat ‘build/test/findbugs’: No such file or directory
mv: cannot stat ‘build/docs/api’: No such file or directory
Build Failed
Build step 'Execute shell' 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-trunk - Build # 3280 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper-trunk/3280/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 95 lines...]
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
6
/home/jenkins/tools/ant/latest/bin/ant clean
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
mv: cannot stat 'build/*.tar.gz': No such file or directory
mv: cannot stat 'build/*.jar': No such file or directory
mv: cannot stat 'build/test/findbugs': No such file or directory
mv: cannot stat 'build/docs/api': No such file or directory
Build Failed
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
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
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: 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



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

ZooKeeper_branch34_jdk8 - Build # 885 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/885/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 247334 lines...]
[junit] 2017-02-14 23:09:02,340 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-02-14 23:09:02,340 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-02-14 23:09:02,340 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-02-14 23:09:02,340 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-02-14 23:09:02,340 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-02-14 23:09:02,341 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-02-14 23:09:02,341 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-14 23:09:02,342 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-02-14 23:09:02,343 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-02-14 23:09:02,344 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-02-14 23:09:02,344 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-02-14 23:09:02,344 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-02-14 23:09:02,345 [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/test4941610589486896079.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test4941610589486896079.junit.dir/version-2
[junit] 2017-02-14 23:09:02,348 [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-02-14 23:09:02,348 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-14 23:09:02,349 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:55886
[junit] 2017-02-14 23:09:02,349 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@838] - Processing 
stat command from /127.0.0.1:55886
[junit] 2017-02-14 23:09:02,349 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-02-14 23:09:02,350 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1019] - Closed socket connection for client 
/127.0.0.1:55886 (no session established for client)
[junit] 2017-02-14 23:09:02,350 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-02-14 23:09:02,352 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-02-14 23:09:02,353 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-02-14 23:09:02,353 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-02-14 23:09:02,353 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-02-14 23:09:02,353 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35515
[junit] 2017-02-14 23:09:02,354 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-02-14 23:09:02,354 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-02-14 23:09:02,354 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-02-14 23:09:02,425 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15a3ee2e6f9 closed
[junit] 2017-02-14 23:09:02,425 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-02-14 23:09:02,425 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15a3ee2e6f9
[junit] 2017-02-14 23:09:02,425 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-02-14 23:09:02,426 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-02-14 23:09:02,426 [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-02-14 23:09:02,426 

[jira] [Commented] (ZOOKEEPER-2691) recreateSocketAddresses may recreate the unreachable IP address

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/173
  
on the surface this pr reminds me of ZOOKEEPER-2184, wondering if some of 
the logic can be shared?  we seem to be solving the same problem of dns 
resolutions not giving the "best" answers in more than one place.


> recreateSocketAddresses may recreate the unreachable IP address
> ---
>
> Key: ZOOKEEPER-2691
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2691
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.8
> Environment: Centos6.5
> Java8
> ZooKeeper3.4.8
>Reporter: JiangJiafu
>Priority: Minor
>
> The QuorumPeer$QuorumServer.recreateSocketAddress()  is used to resolved the 
> hostname to a new IP address(InetAddress) when any exception happens to the 
> socket. It will be very useful when a hostname can be resolved to more than 
> one IP address.
> But the problem is Java API InetAddress.getByName(String hostname) will 
> always return the first IP address when the hostname can be resolved to more 
> than one IP address, and the first IP address may be unreachable forever. For 
> example, if a machine has two network interfaces: eth0, eth1, say eth0 has 
> ip1, eth1 has ip2, the relationship between hostname and the IP addresses is 
> set in /etc/hosts. When I "close" the eth0 by command "ifdown eth0", the 
> InetAddress.getByName(String hostname)  will still return ip1, which is 
> unreachable forever.
> So I think it will be better to check the IP address by 
> InetAddress.isReachable(long) and choose the reachable IP address. 
> I have modified the ZooKeeper source code, and test the new code in my own 
> environment, and it can work very well when I turn down some network 
> interfaces using "ifdown" command.
> The original code is:
> {code:title=QuorumPeer.java|borderStyle=solid}
> public void recreateSocketAddresses() {
> InetAddress address = null;
> try {
> address = InetAddress.getByName(this.hostname);
> LOG.info("Resolved hostname: {} to address: {}", 
> this.hostname, address);
> this.addr = new InetSocketAddress(address, this.port);
> if (this.electionPort > 0){
> this.electionAddr = new InetSocketAddress(address, 
> this.electionPort);
> }
> } catch (UnknownHostException ex) {
> LOG.warn("Failed to resolve address: {}", this.hostname, ex);
> // Have we succeeded in the past?
> if (this.addr != null) {
> // Yes, previously the lookup succeeded. Leave things as 
> they are
> return;
> }
> // The hostname has never resolved. Create our 
> InetSocketAddress(es) as unresolved
> this.addr = InetSocketAddress.createUnresolved(this.hostname, 
> this.port);
> if (this.electionPort > 0){
> this.electionAddr = 
> InetSocketAddress.createUnresolved(this.hostname,
>
> this.electionPort);
> }
> }
> }
> {code}
> After my modification:
> {code:title=QuorumPeer.java|borderStyle=solid}
> public void recreateSocketAddresses() {
> InetAddress address = null;
> try {
> address = getReachableAddress(this.hostname);
> LOG.info("Resolved hostname: {} to address: {}", 
> this.hostname, address);
> this.addr = new InetSocketAddress(address, this.port);
> if (this.electionPort > 0){
> this.electionAddr = new InetSocketAddress(address, 
> this.electionPort);
> }
> } catch (UnknownHostException ex) {
> LOG.warn("Failed to resolve address: {}", this.hostname, ex);
> // Have we succeeded in the past?
> if (this.addr != null) {
> // Yes, previously the lookup succeeded. Leave things as 
> they are
> return;
> }
> // The hostname has never resolved. Create our 
> InetSocketAddress(es) as unresolved
> this.addr = InetSocketAddress.createUnresolved(this.hostname, 
> this.port);
> if (this.electionPort > 0){
> this.electionAddr = 
> InetSocketAddress.createUnresolved(this.hostname,
>
> this.electionPort);
>  

[GitHub] zookeeper issue #173: ZOOKEEPER-2691: recreateSocketAddresses may recreate t...

2017-02-14 Thread afine
Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/173
  
on the surface this pr reminds me of ZOOKEEPER-2184, wondering if some of 
the logic can be shared?  we seem to be solving the same problem of dns 
resolutions not giving the "best" answers in more than one place.


---
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-2687) Deadlock while shutting down the Leader server.

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/176
  
+1 lgtm

looked through he code and i did not see any other places where this 
particular deadlock occurs


> Deadlock while shutting down the Leader server.
> ---
>
> Key: ZOOKEEPER-2687
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2687
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.2, 3.6.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2687-01.patch
>
>
> Leader server enters into deadlock while shutting down. This happens some 
> time only.
> The reason and deadlock flow is same as ZOOKEEPER-2380.
> shutdown was removed from synchronized block in ZOOKEEPER-2380
> Now shutdown is called from synchronized block from another place.
> {code}
> // check leader running status
> if (!this.isRunning()) {
> shutdown("Unexpected internal error");
> return;
> }
> {code}



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


[GitHub] zookeeper issue #176: ZOOKEEPER-2687:Deadlock while shutting down the Leader...

2017-02-14 Thread afine
Github user afine commented on the issue:

https://github.com/apache/zookeeper/pull/176
  
+1 lgtm

looked through he code and i did not see any other places where this 
particular deadlock occurs


---
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-2678) Large databases take a long time to regain a quorum

2017-02-14 Thread Robert Joseph Evans (JIRA)

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

Robert Joseph Evans commented on ZOOKEEPER-2678:


Thanks everyone.  I appreciate the great feedback and the quick turnaround time 
on this.

> Large databases take a long time to regain a quorum
> ---
>
> Key: ZOOKEEPER-2678
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2678
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
> Fix For: 3.4.10, 3.6.0
>
>
> I know this is long but please here me out.
> I recently inherited a massive zookeeper ensemble.  The snapshot is 3.4 GB on 
> disk.  Because of its massive size we have been running into a number of 
> issues. There are lots of problems that we hope to fix with tuning GC etc, 
> but the big one right now that is blocking us making a lot of progress on the 
> rest of them is that when we lose a quorum because the leader left, for what 
> ever reason, it can take well over 5 mins for a new quorum to be established. 
>  So we cannot tune the leader without risking downtime.
> We traced down where the time was being spent and found that each server was 
> clearing the database so it would be read back in again before leader 
> election even started.  Then as part of the sync phase each server will write 
> out a snapshot to checkpoint the progress it made as part of the sync.
> I will be putting up a patch shortly with some proposed changes in it.



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


[jira] [Commented] (ZOOKEEPER-2684) Fix a crashing bug in the mixed workloads commit processor

2017-02-14 Thread Kfir Lev-Ari (JIRA)

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

Kfir Lev-Ari commented on ZOOKEEPER-2684:
-

>From what I understand, seems like a session starts a connection with a 
>smaller cxid than it had in a previous connection?

> Fix a crashing bug in the mixed workloads commit processor
> --
>
> Key: ZOOKEEPER-2684
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2684
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.6.0
> Environment: with pretty heavy load on a real cluster
>Reporter: Ryan Zhang
>Assignee: Ryan Zhang
>Priority: Blocker
> Attachments: ZOOKEEPER-2684.patch
>
>
> We deployed our build with ZOOKEEPER-2024 and it quickly started to crash 
> with the following error
> atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:24:42,305 - ERROR 
> [CommitProcessor:2] 
> -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268)
>  – Got cxid 0x119fa expected 0x11fc5 for client session id 1009079ba470055
> atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:32:04,746 - ERROR 
> [CommitProcessor:2] 
> -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268)
>  – Got cxid 0x698 expected 0x928 for client session id 4002eeb3fd0009d
> atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:34:46,648 - ERROR 
> [CommitProcessor:2] 
> -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268)
>  – Got cxid 0x8904 expected 0x8f34 for client session id 51b8905c90251
> atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:43:46,834 - ERROR 
> [CommitProcessor:2] 
> -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268)
>  – Got cxid 0x3a8d expected 0x3ebc for client session id 2051af11af900cc
> clearly something is not right in the new commit processor per session queue 
> implementation.



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


[jira] [Commented] (ZOOKEEPER-2692) Fix race condition in testWatchAutoResetWithPending

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

GitHub user afine opened a pull request:

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

ZOOKEEPER-2692: Fix race condition in testWatchAutoResetWithPending



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

$ git pull https://github.com/afine/zookeeper ZOOKEEPER-2692_34

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

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


commit b9e1613bee5ca6aa37b45f900dbad8df7d862942
Author: Abraham Fine 
Date:   2017-02-14T21:04:56Z

ZOOKEEPER-2692: Fix race condition in testWatchAutoResetWithPending




> Fix race condition in testWatchAutoResetWithPending
> ---
>
> Key: ZOOKEEPER-2692
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2692
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: tests
>Affects Versions: 3.4.9, 3.5.3, 3.6.0
>Reporter: Abraham Fine
>Assignee: Abraham Fine
>




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


Failed: ZOOKEEPER- PreCommit Build #317

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/317/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 33 lines...]
 > git rev-parse refs/tags/changes/317^{commit} # timeout=10
 > git merge b9e1613bee5ca6aa37b45f900dbad8df7d862942 # timeout=10
 > git rev-parse branch-3.4^{commit} # timeout=10
Checking out Revision b9e1613bee5ca6aa37b45f900dbad8df7d862942 (branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f b9e1613bee5ca6aa37b45f900dbad8df7d862942
 > git rev-parse origin/branch-3.4^{commit} # timeout=10
 > git rev-list 2de93fe450b909ff76ac8bd8fa44296a515845a5 # timeout=10
No emails were triggered.
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[PreCommit-ZOOKEEPER-github-pr-build] $ /bin/bash 
/tmp/hudson2608536374342492900.sh
/home/jenkins/tools/java/latest1.7/bin/java
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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
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
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) 
##
No tests ran.

[GitHub] zookeeper pull request #177: ZOOKEEPER-2692: Fix race condition in testWatch...

2017-02-14 Thread afine
GitHub user afine opened a pull request:

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

ZOOKEEPER-2692: Fix race condition in testWatchAutoResetWithPending



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

$ git pull https://github.com/afine/zookeeper ZOOKEEPER-2692_34

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

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


commit b9e1613bee5ca6aa37b45f900dbad8df7d862942
Author: Abraham Fine 
Date:   2017-02-14T21:04:56Z

ZOOKEEPER-2692: Fix race condition in testWatchAutoResetWithPending




---
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 #165: ZOOKEEPER-2665 Port QA github pull request build to br...

2017-02-14 Thread eolivelli
Github user eolivelli commented on the issue:

https://github.com/apache/zookeeper/pull/165
  
@eribeiro that you for reviewing this.
IMHO it it just a variable name. The script is basically the same as in the 
trunk version. I think it would be better to leave all versions as much similar 
as possible.
Eventually I can change this and file a pr against trunk too but I don't 
know the impact.
@fpj what do you think?


---
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-2665) Port QA github pull request build to branch 3.4 and 3.5

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

Github user eolivelli commented on the issue:

https://github.com/apache/zookeeper/pull/165
  
@eribeiro that you for reviewing this.
IMHO it it just a variable name. The script is basically the same as in the 
trunk version. I think it would be better to leave all versions as much similar 
as possible.
Eventually I can change this and file a pr against trunk too but I don't 
know the impact.
@fpj what do you think?


> Port QA github pull request build to branch 3.4 and 3.5
> ---
>
> Key: ZOOKEEPER-2665
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2665
> Project: ZooKeeper
>  Issue Type: Test
>  Components: build
>Reporter: Flavio Junqueira
> Fix For: 3.5.3, 3.4.11
>
>
> We have QA build for pull requests against master but not against branches 
> 3.4 and 3.5. We need to port the necessary wiring to do it, it shouldn't be 
> difficult.



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


ZooKeeper-trunk-openjdk7 - Build # 1364 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1364/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H14 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-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 -c core.askpass=true fetch --tags --progress 
 > git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 15e3f7fccc770783786e8097f7a6618509bfee0f 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 15e3f7fccc770783786e8097f7a6618509bfee0f
 > git rev-list 15e3f7fccc770783786e8097f7a6618509bfee0f # timeout=10
No emails were triggered.
[ZooKeeper-trunk-openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant 
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml 
-Djavac.target=1.7 clean test-core-java
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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.

[GitHub] zookeeper pull request #165: ZOOKEEPER-2665 Port QA github pull request buil...

2017-02-14 Thread eribeiro
Github user eribeiro commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/165#discussion_r100232542
  
--- Diff: src/java/test/bin/test-github-pr.sh ---
@@ -0,0 +1,616 @@
+#!/usr/bin/env bash
+#   Licensed under the Apache License, Version 2.0 (the "License");
+#   you may not use this file except in compliance with the License.
+#   You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+#   Unless required by applicable law or agreed to in writing, software
+#   distributed under the License is distributed on an "AS IS" BASIS,
+#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
+#   See the License for the specific language governing permissions and
+#   limitations under the License.
+
+
+#set -x
+
+### Setup some variables.
+### GIT_COMMIT and BUILD_URL are set by Hudson if it is run by patch 
process
+### Read variables from properties file
+. `dirname $0`/test-patch.properties
+

+###
+parseArgs() {
+  case "$1" in
+QABUILD)
+  ### Set QABUILD to true to indicate that this script is being run by 
Hudson
+  QABUILD=true
+  if [[ $# != 14 ]] ; then
+echo "ERROR: usage $0 QABUILD
  
   "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$2
+  PS=$3
+  WGET=$4
+  JIRACLI=$5
+  GIT=$6
+  GREP=$7
+  PATCH=$8
+  FINDBUGS_HOME=$9
+  FORREST_HOME=${10}
+  BASEDIR=${11}
+  JIRA_PASSWD=${12}
+  JAVA5_HOME=${13}
+  CURL=${14}
+  if [ ! -e "$PATCH_DIR" ] ; then
+mkdir -p $PATCH_DIR
+  fi
+
+  ## Obtain PR number and title
+  PULLREQUEST_ID=${GIT_PR_NUMBER}
+  PULLREQUEST_TITLE="${GIT_PR_TITLE}"
+
+  ## Extract jira number from PR title
+  local prefix=${PULLREQUEST_TITLE%ZOOKEEPER\-[0-9]*}
+  local noprefix=${PULLREQUEST_TITLE#$prefix}
+  local regex='\(ZOOKEEPER-.[0-9]*\)'
+  defect=$(expr "$noprefix" : ${regex})
+
+  echo "Pull request id: ${PULLREQUEST_ID}"
+  echo "Pull request title: ${PULLREQUEST_TITLE}"
+  echo "Defect number: ${defect}"
+
+  JIRA_COMMENT="GitHub Pull Request ${PULLREQUEST_NUMBER} Build
+  "
+  ;;
+DEVELOPER)
+  ### Set QABUILD to false to indicate that this script is being run 
by a developer
+  QABUILD=false
+  if [[ $# != 10 ]] ; then
+echo "ERROR: usage $0 DEVELOPER   
 
 "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$3
+  PATCH_FILE=${PATCH_DIR}/patch
+  curl -L $2.diff > ${PATCH_FILE}
+  ### PATCH_FILE contains the location of the patchfile
+  if [[ ! -e "$PATCH_FILE" ]] ; then
+echo "Unable to locate the patch file $PATCH_FILE"
+cleanupAndExit 0
+  fi
+  ### Check if $PATCH_DIR exists. If it does not exist, create a new 
directory
+  if [[ ! -e "$PATCH_DIR" ]] ; then
+   mkdir "$PATCH_DIR"
+   if [[ $? == 0 ]] ; then
+ echo "$PATCH_DIR has been created"
+   else
+ echo "Unable to create $PATCH_DIR"
+ cleanupAndExit 0
+   fi
+  fi
+  GIT=$4
+  GREP=$5
+  PATCH=$6
+  FINDBUGS_HOME=$7
+  FORREST_HOME=$8
+  BASEDIR=$9
+  JAVA5_HOME=${10}
+  ### Obtain the patch filename to append it to the version number
+  local subject=`grep "Subject:" ${PATCH_FILE}`
+  local length=`expr match ${subject} ZOOKEEPER-[0-9]*`
+  local position=`expr index ${subject} ZOOKEEPER-`
+  defect=${${subject:$position:$length}#ZOOKEEPER-}
+  ;;
+*)
+  echo "ERROR: usage $0 QABUILD [args] | DEVELOPER [args]"
+  cleanupAndExit 0
+  ;;
+  esac
+}
+

+###
+checkout () {
+  echo ""
+  echo ""
+  echo 
"=="
+  echo 
"=="
+  echo "Testing patch for pull request ${PULLREQUEST_ID}."
+  echo 
"=="
+  echo 
"=="
+  echo ""
+  echo ""
+  ### When run by a developer, if the workspace contains modifications, do 
not continue
+  # Ref http://stackoverflow.com/a/2659808 for details on checking dirty 
status
+  ${GIT} diff-index --quiet HEAD
+  if [[ $? -ne 0 ]] ; then
+

[jira] [Commented] (ZOOKEEPER-2665) Port QA github pull request build to branch 3.4 and 3.5

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

Github user eribeiro commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/165#discussion_r100269721
  
--- Diff: src/java/test/bin/test-github-pr.sh ---
@@ -0,0 +1,616 @@
+#!/usr/bin/env bash
+#   Licensed under the Apache License, Version 2.0 (the "License");
+#   you may not use this file except in compliance with the License.
+#   You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+#   Unless required by applicable law or agreed to in writing, software
+#   distributed under the License is distributed on an "AS IS" BASIS,
+#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
+#   See the License for the specific language governing permissions and
+#   limitations under the License.
+
+
+#set -x
+
+### Setup some variables.
+### GIT_COMMIT and BUILD_URL are set by Hudson if it is run by patch 
process
+### Read variables from properties file
+. `dirname $0`/test-patch.properties
+

+###
+parseArgs() {
+  case "$1" in
+QABUILD)
+  ### Set QABUILD to true to indicate that this script is being run by 
Hudson
+  QABUILD=true
+  if [[ $# != 14 ]] ; then
+echo "ERROR: usage $0 QABUILD
  
   "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$2
+  PS=$3
+  WGET=$4
+  JIRACLI=$5
+  GIT=$6
+  GREP=$7
+  PATCH=$8
+  FINDBUGS_HOME=$9
+  FORREST_HOME=${10}
+  BASEDIR=${11}
+  JIRA_PASSWD=${12}
+  JAVA5_HOME=${13}
--- End diff --

Java6 is the mininum JVM required for branch-3.4, no? And Java7 for 
branch-3.5


> Port QA github pull request build to branch 3.4 and 3.5
> ---
>
> Key: ZOOKEEPER-2665
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2665
> Project: ZooKeeper
>  Issue Type: Test
>  Components: build
>Reporter: Flavio Junqueira
> Fix For: 3.5.3, 3.4.11
>
>
> We have QA build for pull requests against master but not against branches 
> 3.4 and 3.5. We need to port the necessary wiring to do it, it shouldn't be 
> difficult.



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


[jira] [Commented] (ZOOKEEPER-2665) Port QA github pull request build to branch 3.4 and 3.5

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

Github user eribeiro commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/165#discussion_r100269807
  
--- Diff: src/java/test/bin/test-github-pr.sh ---
@@ -0,0 +1,616 @@
+#!/usr/bin/env bash
+#   Licensed under the Apache License, Version 2.0 (the "License");
+#   you may not use this file except in compliance with the License.
+#   You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+#   Unless required by applicable law or agreed to in writing, software
+#   distributed under the License is distributed on an "AS IS" BASIS,
+#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
+#   See the License for the specific language governing permissions and
+#   limitations under the License.
+
+
+#set -x
+
+### Setup some variables.
+### GIT_COMMIT and BUILD_URL are set by Hudson if it is run by patch 
process
+### Read variables from properties file
+. `dirname $0`/test-patch.properties
+

+###
+parseArgs() {
+  case "$1" in
+QABUILD)
+  ### Set QABUILD to true to indicate that this script is being run by 
Hudson
+  QABUILD=true
+  if [[ $# != 14 ]] ; then
+echo "ERROR: usage $0 QABUILD
  
   "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$2
+  PS=$3
+  WGET=$4
+  JIRACLI=$5
+  GIT=$6
+  GREP=$7
+  PATCH=$8
+  FINDBUGS_HOME=$9
+  FORREST_HOME=${10}
+  BASEDIR=${11}
+  JIRA_PASSWD=${12}
+  JAVA5_HOME=${13}
+  CURL=${14}
+  if [ ! -e "$PATCH_DIR" ] ; then
+mkdir -p $PATCH_DIR
+  fi
+
+  ## Obtain PR number and title
+  PULLREQUEST_ID=${GIT_PR_NUMBER}
+  PULLREQUEST_TITLE="${GIT_PR_TITLE}"
+
+  ## Extract jira number from PR title
+  local prefix=${PULLREQUEST_TITLE%ZOOKEEPER\-[0-9]*}
+  local noprefix=${PULLREQUEST_TITLE#$prefix}
+  local regex='\(ZOOKEEPER-.[0-9]*\)'
+  defect=$(expr "$noprefix" : ${regex})
+
+  echo "Pull request id: ${PULLREQUEST_ID}"
+  echo "Pull request title: ${PULLREQUEST_TITLE}"
+  echo "Defect number: ${defect}"
+
+  JIRA_COMMENT="GitHub Pull Request ${PULLREQUEST_NUMBER} Build
+  "
+  ;;
+DEVELOPER)
+  ### Set QABUILD to false to indicate that this script is being run 
by a developer
+  QABUILD=false
+  if [[ $# != 10 ]] ; then
+echo "ERROR: usage $0 DEVELOPER   
 
 "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$3
+  PATCH_FILE=${PATCH_DIR}/patch
+  curl -L $2.diff > ${PATCH_FILE}
+  ### PATCH_FILE contains the location of the patchfile
+  if [[ ! -e "$PATCH_FILE" ]] ; then
+echo "Unable to locate the patch file $PATCH_FILE"
+cleanupAndExit 0
+  fi
+  ### Check if $PATCH_DIR exists. If it does not exist, create a new 
directory
+  if [[ ! -e "$PATCH_DIR" ]] ; then
+   mkdir "$PATCH_DIR"
+   if [[ $? == 0 ]] ; then
+ echo "$PATCH_DIR has been created"
+   else
+ echo "Unable to create $PATCH_DIR"
+ cleanupAndExit 0
+   fi
+  fi
+  GIT=$4
+  GREP=$5
+  PATCH=$6
+  FINDBUGS_HOME=$7
+  FORREST_HOME=$8
+  BASEDIR=$9
+  JAVA5_HOME=${10}
--- End diff --

As above.


> Port QA github pull request build to branch 3.4 and 3.5
> ---
>
> Key: ZOOKEEPER-2665
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2665
> Project: ZooKeeper
>  Issue Type: Test
>  Components: build
>Reporter: Flavio Junqueira
> Fix For: 3.5.3, 3.4.11
>
>
> We have QA build for pull requests against master but not against branches 
> 3.4 and 3.5. We need to port the necessary wiring to do it, it shouldn't be 
> difficult.



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


[jira] [Commented] (ZOOKEEPER-2665) Port QA github pull request build to branch 3.4 and 3.5

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

Github user eribeiro commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/165#discussion_r100232542
  
--- Diff: src/java/test/bin/test-github-pr.sh ---
@@ -0,0 +1,616 @@
+#!/usr/bin/env bash
+#   Licensed under the Apache License, Version 2.0 (the "License");
+#   you may not use this file except in compliance with the License.
+#   You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+#   Unless required by applicable law or agreed to in writing, software
+#   distributed under the License is distributed on an "AS IS" BASIS,
+#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
+#   See the License for the specific language governing permissions and
+#   limitations under the License.
+
+
+#set -x
+
+### Setup some variables.
+### GIT_COMMIT and BUILD_URL are set by Hudson if it is run by patch 
process
+### Read variables from properties file
+. `dirname $0`/test-patch.properties
+

+###
+parseArgs() {
+  case "$1" in
+QABUILD)
+  ### Set QABUILD to true to indicate that this script is being run by 
Hudson
+  QABUILD=true
+  if [[ $# != 14 ]] ; then
+echo "ERROR: usage $0 QABUILD
  
   "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$2
+  PS=$3
+  WGET=$4
+  JIRACLI=$5
+  GIT=$6
+  GREP=$7
+  PATCH=$8
+  FINDBUGS_HOME=$9
+  FORREST_HOME=${10}
+  BASEDIR=${11}
+  JIRA_PASSWD=${12}
+  JAVA5_HOME=${13}
+  CURL=${14}
+  if [ ! -e "$PATCH_DIR" ] ; then
+mkdir -p $PATCH_DIR
+  fi
+
+  ## Obtain PR number and title
+  PULLREQUEST_ID=${GIT_PR_NUMBER}
+  PULLREQUEST_TITLE="${GIT_PR_TITLE}"
+
+  ## Extract jira number from PR title
+  local prefix=${PULLREQUEST_TITLE%ZOOKEEPER\-[0-9]*}
+  local noprefix=${PULLREQUEST_TITLE#$prefix}
+  local regex='\(ZOOKEEPER-.[0-9]*\)'
+  defect=$(expr "$noprefix" : ${regex})
+
+  echo "Pull request id: ${PULLREQUEST_ID}"
+  echo "Pull request title: ${PULLREQUEST_TITLE}"
+  echo "Defect number: ${defect}"
+
+  JIRA_COMMENT="GitHub Pull Request ${PULLREQUEST_NUMBER} Build
+  "
+  ;;
+DEVELOPER)
+  ### Set QABUILD to false to indicate that this script is being run 
by a developer
+  QABUILD=false
+  if [[ $# != 10 ]] ; then
+echo "ERROR: usage $0 DEVELOPER   
 
 "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$3
+  PATCH_FILE=${PATCH_DIR}/patch
+  curl -L $2.diff > ${PATCH_FILE}
+  ### PATCH_FILE contains the location of the patchfile
+  if [[ ! -e "$PATCH_FILE" ]] ; then
+echo "Unable to locate the patch file $PATCH_FILE"
+cleanupAndExit 0
+  fi
+  ### Check if $PATCH_DIR exists. If it does not exist, create a new 
directory
+  if [[ ! -e "$PATCH_DIR" ]] ; then
+   mkdir "$PATCH_DIR"
+   if [[ $? == 0 ]] ; then
+ echo "$PATCH_DIR has been created"
+   else
+ echo "Unable to create $PATCH_DIR"
+ cleanupAndExit 0
+   fi
+  fi
+  GIT=$4
+  GREP=$5
+  PATCH=$6
+  FINDBUGS_HOME=$7
+  FORREST_HOME=$8
+  BASEDIR=$9
+  JAVA5_HOME=${10}
+  ### Obtain the patch filename to append it to the version number
+  local subject=`grep "Subject:" ${PATCH_FILE}`
+  local length=`expr match ${subject} ZOOKEEPER-[0-9]*`
+  local position=`expr index ${subject} ZOOKEEPER-`
+  defect=${${subject:$position:$length}#ZOOKEEPER-}
+  ;;
+*)
+  echo "ERROR: usage $0 QABUILD [args] | DEVELOPER [args]"
+  cleanupAndExit 0
+  ;;
+  esac
+}
+

+###
+checkout () {
+  echo ""
+  echo ""
+  echo 
"=="
+  echo 
"=="
+  echo "Testing patch for pull request ${PULLREQUEST_ID}."
+  echo 
"=="
+  echo 
"=="
+  echo ""
+  echo ""
+  ### When run by a 

[GitHub] zookeeper pull request #165: ZOOKEEPER-2665 Port QA github pull request buil...

2017-02-14 Thread eribeiro
Github user eribeiro commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/165#discussion_r100269807
  
--- Diff: src/java/test/bin/test-github-pr.sh ---
@@ -0,0 +1,616 @@
+#!/usr/bin/env bash
+#   Licensed under the Apache License, Version 2.0 (the "License");
+#   you may not use this file except in compliance with the License.
+#   You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+#   Unless required by applicable law or agreed to in writing, software
+#   distributed under the License is distributed on an "AS IS" BASIS,
+#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
+#   See the License for the specific language governing permissions and
+#   limitations under the License.
+
+
+#set -x
+
+### Setup some variables.
+### GIT_COMMIT and BUILD_URL are set by Hudson if it is run by patch 
process
+### Read variables from properties file
+. `dirname $0`/test-patch.properties
+

+###
+parseArgs() {
+  case "$1" in
+QABUILD)
+  ### Set QABUILD to true to indicate that this script is being run by 
Hudson
+  QABUILD=true
+  if [[ $# != 14 ]] ; then
+echo "ERROR: usage $0 QABUILD
  
   "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$2
+  PS=$3
+  WGET=$4
+  JIRACLI=$5
+  GIT=$6
+  GREP=$7
+  PATCH=$8
+  FINDBUGS_HOME=$9
+  FORREST_HOME=${10}
+  BASEDIR=${11}
+  JIRA_PASSWD=${12}
+  JAVA5_HOME=${13}
+  CURL=${14}
+  if [ ! -e "$PATCH_DIR" ] ; then
+mkdir -p $PATCH_DIR
+  fi
+
+  ## Obtain PR number and title
+  PULLREQUEST_ID=${GIT_PR_NUMBER}
+  PULLREQUEST_TITLE="${GIT_PR_TITLE}"
+
+  ## Extract jira number from PR title
+  local prefix=${PULLREQUEST_TITLE%ZOOKEEPER\-[0-9]*}
+  local noprefix=${PULLREQUEST_TITLE#$prefix}
+  local regex='\(ZOOKEEPER-.[0-9]*\)'
+  defect=$(expr "$noprefix" : ${regex})
+
+  echo "Pull request id: ${PULLREQUEST_ID}"
+  echo "Pull request title: ${PULLREQUEST_TITLE}"
+  echo "Defect number: ${defect}"
+
+  JIRA_COMMENT="GitHub Pull Request ${PULLREQUEST_NUMBER} Build
+  "
+  ;;
+DEVELOPER)
+  ### Set QABUILD to false to indicate that this script is being run 
by a developer
+  QABUILD=false
+  if [[ $# != 10 ]] ; then
+echo "ERROR: usage $0 DEVELOPER   
 
 "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$3
+  PATCH_FILE=${PATCH_DIR}/patch
+  curl -L $2.diff > ${PATCH_FILE}
+  ### PATCH_FILE contains the location of the patchfile
+  if [[ ! -e "$PATCH_FILE" ]] ; then
+echo "Unable to locate the patch file $PATCH_FILE"
+cleanupAndExit 0
+  fi
+  ### Check if $PATCH_DIR exists. If it does not exist, create a new 
directory
+  if [[ ! -e "$PATCH_DIR" ]] ; then
+   mkdir "$PATCH_DIR"
+   if [[ $? == 0 ]] ; then
+ echo "$PATCH_DIR has been created"
+   else
+ echo "Unable to create $PATCH_DIR"
+ cleanupAndExit 0
+   fi
+  fi
+  GIT=$4
+  GREP=$5
+  PATCH=$6
+  FINDBUGS_HOME=$7
+  FORREST_HOME=$8
+  BASEDIR=$9
+  JAVA5_HOME=${10}
--- End diff --

As above.


---
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 pull request #165: ZOOKEEPER-2665 Port QA github pull request buil...

2017-02-14 Thread eribeiro
Github user eribeiro commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/165#discussion_r100269721
  
--- Diff: src/java/test/bin/test-github-pr.sh ---
@@ -0,0 +1,616 @@
+#!/usr/bin/env bash
+#   Licensed under the Apache License, Version 2.0 (the "License");
+#   you may not use this file except in compliance with the License.
+#   You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+#   Unless required by applicable law or agreed to in writing, software
+#   distributed under the License is distributed on an "AS IS" BASIS,
+#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
+#   See the License for the specific language governing permissions and
+#   limitations under the License.
+
+
+#set -x
+
+### Setup some variables.
+### GIT_COMMIT and BUILD_URL are set by Hudson if it is run by patch 
process
+### Read variables from properties file
+. `dirname $0`/test-patch.properties
+

+###
+parseArgs() {
+  case "$1" in
+QABUILD)
+  ### Set QABUILD to true to indicate that this script is being run by 
Hudson
+  QABUILD=true
+  if [[ $# != 14 ]] ; then
+echo "ERROR: usage $0 QABUILD
  
   "
+cleanupAndExit 0
+  fi
+  PATCH_DIR=$2
+  PS=$3
+  WGET=$4
+  JIRACLI=$5
+  GIT=$6
+  GREP=$7
+  PATCH=$8
+  FINDBUGS_HOME=$9
+  FORREST_HOME=${10}
+  BASEDIR=${11}
+  JIRA_PASSWD=${12}
+  JAVA5_HOME=${13}
--- End diff --

Java6 is the mininum JVM required for branch-3.4, no? And Java7 for 
branch-3.5


---
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 - Build # 1836 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34/1836/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 58 lines...]
  collisions:0 txqueuelen:0 
  RX bytes:2374962052708 (2.3 TB)  TX bytes:2374962052708 (2.3 TB)

core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 386177
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
6
/home/jenkins/tools/ant/latest/bin/ant clean
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
mv: cannot stat ‘build/*.tar.gz’: No such file or directory
mv: cannot stat ‘build/*.jar’: No such file or directory
mv: cannot stat ‘build/test/findbugs’: No such file or directory
mv: cannot stat ‘build/docs/api’: No such file or directory
Build Failed
Build step 'Execute shell' 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.

Re: Jenkins failing on pull request

2017-02-14 Thread Michael Han
The failure is expected because this PR is targeting branch-3.4 where the
triggers for pre-commit workflow is not ready.
https://github.com/apache/zookeeper/pull/165 is created to address that
issue. If anyone has time to review this that would be great.

On Tue, Feb 14, 2017 at 10:57 AM, Yan Fitterer  wrote:

> Hi, I submitted PR #166  a
> few days ago, but Jenkins seems to have had a blip  <
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-
> github-pr-build/288/console>on github PR build #288 (Target
> "qa-test-pullrequest" does not exist in the project "ZooKeeper”).
>
> How should I proceed ? New PR ? Else can somebody kick the Jenkins build
> in that PR ? It looks to me like something went wrong with ant on that
> build attempt, but maybe I’m missing something.




-- 
Cheers
Michael.


ZooKeeper_branch34_openjdk7 - Build # 1392 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1392/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-eu2 (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 -c core.askpass=true 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 2de93fe450b909ff76ac8bd8fa44296a515845a5 
(refs/remotes/origin/branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 2de93fe450b909ff76ac8bd8fa44296a515845a5
 > git rev-list e8247eec1103e387e02bbb1e8859b4d468688f48 # timeout=10
No emails were triggered.
[ZooKeeper_branch34_openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant 
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml 
-Djavac.target=1.7 clean test-core-java
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:442)
at java.net.URLClassLoader.access$100(URLClassLoader.java:64)
at java.net.URLClassLoader$1.run(URLClassLoader.java:354)
at java.net.URLClassLoader$1.run(URLClassLoader.java:348)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:347)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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 # 884 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/884/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 240807 lines...]
[junit] 2017-02-14 19:11:08,514 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-02-14 19:11:08,514 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-02-14 19:11:08,514 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-02-14 19:11:08,514 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-02-14 19:11:08,514 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-02-14 19:11:08,515 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-02-14 19:11:08,515 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-14 19:11:08,515 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-02-14 19:11:08,516 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-02-14 19:11:08,516 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-02-14 19:11:08,517 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-02-14 19:11:08,517 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-02-14 19:11:08,517 [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/test9116442628310762992.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test9116442628310762992.junit.dir/version-2
[junit] 2017-02-14 19:11:08,519 [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-02-14 19:11:08,519 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-14 19:11:08,520 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:45010
[junit] 2017-02-14 19:11:08,520 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@838] - Processing 
stat command from /127.0.0.1:45010
[junit] 2017-02-14 19:11:08,520 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-02-14 19:11:08,520 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1019] - Closed socket connection for client 
/127.0.0.1:45010 (no session established for client)
[junit] 2017-02-14 19:11:08,520 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-02-14 19:11:08,522 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-02-14 19:11:08,522 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-02-14 19:11:08,522 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-02-14 19:11:08,522 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-02-14 19:11:08,522 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35517
[junit] 2017-02-14 19:11:08,523 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-02-14 19:11:08,523 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-02-14 19:11:08,523 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-02-14 19:11:08,603 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15a3e091a64 closed
[junit] 2017-02-14 19:11:08,603 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15a3e091a64
[junit] 2017-02-14 19:11:08,603 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-02-14 19:11:08,604 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-02-14 19:11:08,604 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-02-14 19:11:08,604 [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-02-14 19:11:08,604 

Jenkins failing on pull request

2017-02-14 Thread Yan Fitterer
Hi, I submitted PR #166  a few 
days ago, but Jenkins seems to have had a blip  
on
 github PR build #288 (Target "qa-test-pullrequest" does not exist in the 
project "ZooKeeper”).

How should I proceed ? New PR ? Else can somebody kick the Jenkins build in 
that PR ? It looks to me like something went wrong with ant on that build 
attempt, but maybe I’m missing something.

ZooKeeper_branch34_solaris - Build # 1473 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1473/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 196302 lines...]
[junit] 2017-02-14 18:56:01,613 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-02-14 18:56:01,614 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-02-14 18:56:01,614 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-02-14 18:56:01,614 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-02-14 18:56:01,614 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-02-14 18:56:01,614 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-14 18:56:01,615 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-02-14 18:56:01,619 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-02-14 18:56:01,620 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-02-14 18:56:01,621 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-02-14 18:56:01,622 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-02-14 18:56:01,623 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/test/tmp/test7563789512153337856.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/build/test/tmp/test7563789512153337856.junit.dir/version-2
[junit] 2017-02-14 18:56:01,626 [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-02-14 18:56:01,626 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-14 18:56:01,627 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:37998
[junit] 2017-02-14 18:56:01,627 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@838] - Processing 
stat command from /127.0.0.1:37998
[junit] 2017-02-14 18:56:01,627 [myid:] - INFO  
[Thread-5:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-02-14 18:56:01,628 [myid:] - INFO  
[Thread-5:NIOServerCnxn@1019] - Closed socket connection for client 
/127.0.0.1:37998 (no session established for client)
[junit] 2017-02-14 18:56:01,628 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-02-14 18:56:01,629 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-02-14 18:56:01,629 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-02-14 18:56:01,629 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-02-14 18:56:01,630 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-02-14 18:56:01,630 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 9182
[junit] 2017-02-14 18:56:01,630 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-02-14 18:56:01,630 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-02-14 18:56:01,630 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-02-14 18:56:01,701 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15a3dfb43a0 closed
[junit] 2017-02-14 18:56:01,702 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-02-14 18:56:01,702 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15a3dfb43a0
[junit] 2017-02-14 18:56:01,703 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-02-14 18:56:01,703 [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-02-14 18:56:01,703 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-02-14 18:56:01,703 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-02-14 18:56:01,703 

ZooKeeper_branch34_jdk7 - Build # 1406 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1406/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 243035 lines...]
[junit] 2017-02-14 18:42:01,352 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2017-02-14 18:42:01,353 [myid:] - INFO  
[main:PrepRequestProcessor@764] - Shutting down
[junit] 2017-02-14 18:42:01,353 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2017-02-14 18:42:01,353 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2017-02-14 18:42:01,354 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2017-02-14 18:42:01,354 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2017-02-14 18:42:01,354 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-14 18:42:01,355 [myid:] - INFO  [main:JMXEnv@147] - 
ensureOnly:[]
[junit] 2017-02-14 18:42:01,357 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2017-02-14 18:42:01,357 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2017-02-14 18:42:01,358 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2017-02-14 18:42:01,358 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2017-02-14 18:42:01,358 [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/test8791374394843758832.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test8791374394843758832.junit.dir/version-2
[junit] 2017-02-14 18:42:01,363 [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-02-14 18:42:01,364 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2017-02-14 18:42:01,364 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:54614
[junit] 2017-02-14 18:42:01,365 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@838] - Processing 
stat command from /127.0.0.1:54614
[junit] 2017-02-14 18:42:01,365 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output
[junit] 2017-02-14 18:42:01,366 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1019] - Closed socket connection for client 
/127.0.0.1:54614 (no session established for client)
[junit] 2017-02-14 18:42:01,366 [myid:] - INFO  [main:JMXEnv@230] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-02-14 18:42:01,368 [myid:] - INFO  [main:JMXEnv@247] - 
expect:InMemoryDataTree
[junit] 2017-02-14 18:42:01,368 [myid:] - INFO  [main:JMXEnv@251] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2017-02-14 18:42:01,369 [myid:] - INFO  [main:JMXEnv@247] - 
expect:StandaloneServer_port
[junit] 2017-02-14 18:42:01,369 [myid:] - INFO  [main:JMXEnv@251] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2017-02-14 18:42:01,369 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35674
[junit] 2017-02-14 18:42:01,369 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2017-02-14 18:42:01,369 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2017-02-14 18:42:01,370 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2017-02-14 18:42:01,434 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15a3dee716f closed
[junit] 2017-02-14 18:42:01,434 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2017-02-14 18:42:01,435 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x15a3dee716f
[junit] 2017-02-14 18:42:01,435 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2017-02-14 18:42:01,435 [myid:] - INFO  [main:ZooKeeperServer@505] 
- shutting down
[junit] 2017-02-14 18:42:01,435 [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-02-14 

[jira] [Comment Edited] (ZOOKEEPER-2684) Fix a crashing bug in the mixed workloads commit processor

2017-02-14 Thread Ryan Zhang (JIRA)

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

Ryan Zhang edited comment on ZOOKEEPER-2684 at 2/14/17 6:20 PM:


Unfortunately, this is only half of the story. I tested the build and see the 
following crash

atla-cbo-26-sr4.prod.twttr.net:  2017-02-14 17:55:42,323 - ERROR 
[CommitProcessor:4] - Severe unrecoverable error, from thread : 
CommitProcessor:4
atla-cbo-26-sr4.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbo-26-sr4.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbo-26-sr4.prod.twttr.net:  2017-02-14 18:12:25,515 - ERROR 
[CommitProcessor:4] - Got request sessionid:0x40069edcb5b7b7f type:create 
cxid:0x36 zxid:0x38205009d26 txntype:1 reqpath:n/a
atla-cbo-26-sr4.prod.twttr.net:   but we are expecting request 
sessionid:0x40069edcb5b7b7f type:delete cxid:0x30 zxid:0xfffe 
txntype:unknown reqpath:/loadgen/load_1759491424
atla-cbo-26-sr4.prod.twttr.net:  


Stay tuned, I am adding back the verbose logs and will report on what I found


was (Author: nerdyyatrice):
Unfortunately, this is only half of the story. I tested the build and see the 
following crash

atla-avu-37-sr1.prod.twttr.net:  2017-02-14 15:04:06,180 - ERROR 
[CommitProcessor:5] - Severe unrecoverable error, from thread : 
CommitProcessor:5
atla-avu-37-sr1.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-avu-37-sr1.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)

Stay tuned, I am adding back the verbose logs and will report on what I found

> Fix a crashing bug in the mixed workloads commit processor
> --
>
> Key: ZOOKEEPER-2684
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2684
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.6.0
> Environment: with pretty heavy load on a real cluster
>Reporter: Ryan Zhang
>Assignee: Ryan Zhang
>Priority: Blocker
> Attachments: ZOOKEEPER-2684.patch
>
>
> We deployed our build with ZOOKEEPER-2024 and it quickly started to crash 
> with the following error
> atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:24:42,305 - ERROR 
> [CommitProcessor:2] 
> -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268)
>  – Got cxid 0x119fa expected 0x11fc5 for client session id 1009079ba470055
> atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:32:04,746 - ERROR 
> [CommitProcessor:2] 
> -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268)
>  – Got cxid 0x698 expected 0x928 for client session id 4002eeb3fd0009d
> atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:34:46,648 - ERROR 
> [CommitProcessor:2] 
> -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268)
>  – Got cxid 0x8904 expected 0x8f34 for client session id 51b8905c90251
> atla-buh-05-sr1.prod.twttr.net: 2017-01-18 22:43:46,834 - ERROR 
> [CommitProcessor:2] 
> -org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:268)
>  – Got cxid 0x3a8d expected 0x3ebc for client session id 2051af11af900cc
> clearly something is not right in the new commit processor per session queue 
> implementation.



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


[jira] [Comment Edited] (ZOOKEEPER-2684) Fix a crashing bug in the mixed workloads commit processor

2017-02-14 Thread Ryan Zhang (JIRA)

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

Ryan Zhang edited comment on ZOOKEEPER-2684 at 2/14/17 6:19 PM:


Unfortunately, this is only half of the story. I tested the build and see the 
following crash

atla-avu-37-sr1.prod.twttr.net:  2017-02-14 15:04:06,180 - ERROR 
[CommitProcessor:5] - Severe unrecoverable error, from thread : 
CommitProcessor:5
atla-avu-37-sr1.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-avu-37-sr1.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)

Stay tuned, I am adding back the verbose logs and will report on what I found


was (Author: nerdyyatrice):
Unfortunately, this is only half of the story. I tested the build and see the 
following crash

atla-avu-37-sr1.prod.twttr.net:  2017-02-14 15:04:06,180 - ERROR 
[CommitProcessor:5] - Severe unrecoverable error, from thread : 
CommitProcessor:5
atla-avu-37-sr1.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-avu-37-sr1.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbn-19-sr1.prod.twttr.net:  
atla-cbn-19-sr1.prod.twttr.net:  2017-02-14 17:55:04,020 - ERROR 
[CommitProcessor:3] - Severe unrecoverable error, from thread : 
CommitProcessor:3
atla-cbn-19-sr1.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbn-19-sr1.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbn-19-sr1.prod.twttr.net:  2017-02-14 18:02:12,019 - ERROR 
[CommitProcessor:3] - Got request sessionid:0x30069d48d4909da type:error 
cxid:0x9ca zxid:0x38204ef60ad txntype:-1 reqpath:n/a
atla-cbn-19-sr1.prod.twttr.net:   but we are expecting request 
sessionid:0x30069d48d4909da type:create cxid:0x9c9 zxid:0xfffe 
txntype:unknown reqpath:/loadgen/load_
atla-cbn-19-sr1.prod.twttr.net:  
atla-cbn-19-sr1.prod.twttr.net:  2017-02-14 18:02:12,019 - ERROR 
[CommitProcessor:3] - Severe unrecoverable error, from thread : 
CommitProcessor:3
atla-cbn-19-sr1.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbn-19-sr1.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbo-26-sr4.prod.twttr.net:  
atla-cbo-26-sr4.prod.twttr.net:  2017-02-14 17:55:42,323 - ERROR 
[CommitProcessor:4] - Severe unrecoverable error, from thread : 
CommitProcessor:4
atla-cbo-26-sr4.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbo-26-sr4.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbo-26-sr4.prod.twttr.net:  2017-02-14 18:12:25,515 - ERROR 
[CommitProcessor:4] - Got request sessionid:0x40069edcb5b7b7f type:create 
cxid:0x36 zxid:0x38205009d26 txntype:1 reqpath:n/a
atla-cbo-26-sr4.prod.twttr.net:   but we are expecting request 
sessionid:0x40069edcb5b7b7f type:delete cxid:0x30 zxid:0xfffe 
txntype:unknown reqpath:/loadgen/load_1759491424
atla-cbo-26-sr4.prod.twttr.net:  
atla-cbo-26-sr4.prod.twttr.net:  2017-02-14 18:12:25,516 - ERROR 
[CommitProcessor:4] - Severe unrecoverable error, from thread : 
CommitProcessor:4
atla-cbo-26-sr4.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbo-26-sr4.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbs-11-sr2.prod.twttr.net:  
atla-cbs-11-sr2.prod.twttr.net:  2017-02-14 17:58:06,370 - ERROR 
[CommitProcessor:2] - Severe unrecoverable error, from thread : 
CommitProcessor:2
atla-cbs-11-sr2.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbs-11-sr2.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbs-11-sr2.prod.twttr.net:  2017-02-14 18:09:41,178 - ERROR 
[CommitProcessor:2] - Got request sessionid:0x20069efe2da8afa type:error 
cxid:0x295 zxid:0x38204fc2277 txntype:-1 reqpath:n/a
atla-cbs-11-sr2.prod.twttr.net:   but we are expecting request 
sessionid:0x20069efe2da8afa type:delete cxid:0x291 zxid:0xfffe 
txntype:unknown reqpath:/loadgen/load_1759352322
atla-cbs-11-sr2.prod.twttr.net:  
atla-cbs-11-sr2.prod.twttr.net:  2017-02-14 18:09:41,178 - ERROR 
[CommitProcessor:2] - Severe unrecoverable error, from thread : 
CommitProcessor:2

[jira] [Commented] (ZOOKEEPER-2684) Fix a crashing bug in the mixed workloads commit processor

2017-02-14 Thread Ryan Zhang (JIRA)

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

Ryan Zhang commented on ZOOKEEPER-2684:
---

Unfortunately, this is only half of the story. I tested the build and see the 
following crash

atla-avu-37-sr1.prod.twttr.net:  2017-02-14 15:04:06,180 - ERROR 
[CommitProcessor:5] - Severe unrecoverable error, from thread : 
CommitProcessor:5
atla-avu-37-sr1.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-avu-37-sr1.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbn-19-sr1.prod.twttr.net:  
atla-cbn-19-sr1.prod.twttr.net:  2017-02-14 17:55:04,020 - ERROR 
[CommitProcessor:3] - Severe unrecoverable error, from thread : 
CommitProcessor:3
atla-cbn-19-sr1.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbn-19-sr1.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbn-19-sr1.prod.twttr.net:  2017-02-14 18:02:12,019 - ERROR 
[CommitProcessor:3] - Got request sessionid:0x30069d48d4909da type:error 
cxid:0x9ca zxid:0x38204ef60ad txntype:-1 reqpath:n/a
atla-cbn-19-sr1.prod.twttr.net:   but we are expecting request 
sessionid:0x30069d48d4909da type:create cxid:0x9c9 zxid:0xfffe 
txntype:unknown reqpath:/loadgen/load_
atla-cbn-19-sr1.prod.twttr.net:  
atla-cbn-19-sr1.prod.twttr.net:  2017-02-14 18:02:12,019 - ERROR 
[CommitProcessor:3] - Severe unrecoverable error, from thread : 
CommitProcessor:3
atla-cbn-19-sr1.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbn-19-sr1.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbo-26-sr4.prod.twttr.net:  
atla-cbo-26-sr4.prod.twttr.net:  2017-02-14 17:55:42,323 - ERROR 
[CommitProcessor:4] - Severe unrecoverable error, from thread : 
CommitProcessor:4
atla-cbo-26-sr4.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbo-26-sr4.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbo-26-sr4.prod.twttr.net:  2017-02-14 18:12:25,515 - ERROR 
[CommitProcessor:4] - Got request sessionid:0x40069edcb5b7b7f type:create 
cxid:0x36 zxid:0x38205009d26 txntype:1 reqpath:n/a
atla-cbo-26-sr4.prod.twttr.net:   but we are expecting request 
sessionid:0x40069edcb5b7b7f type:delete cxid:0x30 zxid:0xfffe 
txntype:unknown reqpath:/loadgen/load_1759491424
atla-cbo-26-sr4.prod.twttr.net:  
atla-cbo-26-sr4.prod.twttr.net:  2017-02-14 18:12:25,516 - ERROR 
[CommitProcessor:4] - Severe unrecoverable error, from thread : 
CommitProcessor:4
atla-cbo-26-sr4.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbo-26-sr4.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbs-11-sr2.prod.twttr.net:  
atla-cbs-11-sr2.prod.twttr.net:  2017-02-14 17:58:06,370 - ERROR 
[CommitProcessor:2] - Severe unrecoverable error, from thread : 
CommitProcessor:2
atla-cbs-11-sr2.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbs-11-sr2.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cbs-11-sr2.prod.twttr.net:  2017-02-14 18:09:41,178 - ERROR 
[CommitProcessor:2] - Got request sessionid:0x20069efe2da8afa type:error 
cxid:0x295 zxid:0x38204fc2277 txntype:-1 reqpath:n/a
atla-cbs-11-sr2.prod.twttr.net:   but we are expecting request 
sessionid:0x20069efe2da8afa type:delete cxid:0x291 zxid:0xfffe 
txntype:unknown reqpath:/loadgen/load_1759352322
atla-cbs-11-sr2.prod.twttr.net:  
atla-cbs-11-sr2.prod.twttr.net:  2017-02-14 18:09:41,178 - ERROR 
[CommitProcessor:2] - Severe unrecoverable error, from thread : 
CommitProcessor:2
atla-cbs-11-sr2.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cbs-11-sr2.prod.twttr.net: at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:276)
atla-cdc-11-sr2.prod.twttr.net:  
atla-cdc-11-sr2.prod.twttr.net:  2017-02-14 17:50:49,359 - ERROR 
[CommitProcessor:1] - Severe unrecoverable error, from thread : 
CommitProcessor:1
atla-cdc-11-sr2.prod.twttr.net:  
org.apache.zookeeper.KeeperException$RuntimeInconsistencyException: 
KeeperErrorCode = RuntimeInconsistency
atla-cdc-11-sr2.prod.twttr.net: at 

[jira] [Commented] (ZOOKEEPER-2678) Large databases take a long time to regain a quorum

2017-02-14 Thread Michael Han (JIRA)

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

Michael Han commented on ZOOKEEPER-2678:


Merged to 3.4: 
https://github.com/apache/zookeeper/commit/2de93fe450b909ff76ac8bd8fa44296a515845a5.
cc [~rakeshr].

> Large databases take a long time to regain a quorum
> ---
>
> Key: ZOOKEEPER-2678
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2678
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
> Fix For: 3.4.10, 3.6.0
>
>
> I know this is long but please here me out.
> I recently inherited a massive zookeeper ensemble.  The snapshot is 3.4 GB on 
> disk.  Because of its massive size we have been running into a number of 
> issues. There are lots of problems that we hope to fix with tuning GC etc, 
> but the big one right now that is blocking us making a lot of progress on the 
> rest of them is that when we lose a quorum because the leader left, for what 
> ever reason, it can take well over 5 mins for a new quorum to be established. 
>  So we cannot tune the leader without risking downtime.
> We traced down where the time was being spent and found that each server was 
> clearing the database so it would be read back in again before leader 
> election even started.  Then as part of the sync phase each server will write 
> out a snapshot to checkpoint the progress it made as part of the sync.
> I will be putting up a patch shortly with some proposed changes in it.



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


Failed: ZOOKEEPER- PreCommit Build #316

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/316/

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

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1699)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1695)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1317)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$3.execute(CliGitAPIImpl.java:587)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.merge(AbstractGitAPIImpl.java:87)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.merge(CliGitAPIImpl.java:63)
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:884)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:859)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:818)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
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:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249)
at com.sun.proxy.$Proxy92.merge(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.merge(RemoteGitImpl.java:438)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:107)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:984)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1087)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
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:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
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 

[jira] [Resolved] (ZOOKEEPER-2678) Large databases take a long time to regain a quorum

2017-02-14 Thread Michael Han (JIRA)

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

Michael Han resolved ZOOKEEPER-2678.

   Resolution: Fixed
Fix Version/s: 3.4.10

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

> Large databases take a long time to regain a quorum
> ---
>
> Key: ZOOKEEPER-2678
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2678
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
> Fix For: 3.6.0, 3.4.10
>
>
> I know this is long but please here me out.
> I recently inherited a massive zookeeper ensemble.  The snapshot is 3.4 GB on 
> disk.  Because of its massive size we have been running into a number of 
> issues. There are lots of problems that we hope to fix with tuning GC etc, 
> but the big one right now that is blocking us making a lot of progress on the 
> rest of them is that when we lose a quorum because the leader left, for what 
> ever reason, it can take well over 5 mins for a new quorum to be established. 
>  So we cannot tune the leader without risking downtime.
> We traced down where the time was being spent and found that each server was 
> clearing the database so it would be read back in again before leader 
> election even started.  Then as part of the sync phase each server will write 
> out a snapshot to checkpoint the progress it made as part of the sync.
> I will be putting up a patch shortly with some proposed changes in it.



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


Failed: ZOOKEEPER- PreCommit Build #315

2017-02-14 Thread Apache Jenkins Server
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/315/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 30 lines...]
at hudson.remoting.Request$2.run(Request.java:332)
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:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249)
at com.sun.proxy.$Proxy92.checkoutBranch(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:327)
at 
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:984)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1087)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
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:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
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:1723)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1699)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1695)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1317)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1329)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1979)
at 
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:63)
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:884)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:859)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:818)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
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-2678) Large databases take a long time to regain a quorum

2017-02-14 Thread ASF GitHub Bot (JIRA)

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

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

Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/157
  
Thanks @revans2 for the useful results. I spend sometime going through the 
changes and looks good to me. @hanm, please go ahead with merging this to 
branch-3.4.


> Large databases take a long time to regain a quorum
> ---
>
> Key: ZOOKEEPER-2678
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2678
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.9, 3.5.2
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
> Fix For: 3.6.0
>
>
> I know this is long but please here me out.
> I recently inherited a massive zookeeper ensemble.  The snapshot is 3.4 GB on 
> disk.  Because of its massive size we have been running into a number of 
> issues. There are lots of problems that we hope to fix with tuning GC etc, 
> but the big one right now that is blocking us making a lot of progress on the 
> rest of them is that when we lose a quorum because the leader left, for what 
> ever reason, it can take well over 5 mins for a new quorum to be established. 
>  So we cannot tune the leader without risking downtime.
> We traced down where the time was being spent and found that each server was 
> clearing the database so it would be read back in again before leader 
> election even started.  Then as part of the sync phase each server will write 
> out a snapshot to checkpoint the progress it made as part of the sync.
> I will be putting up a patch shortly with some proposed changes in it.



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


[GitHub] zookeeper issue #157: ZOOKEEPER-2678: Discovery and Sync can take a very lon...

2017-02-14 Thread rakeshadr
Github user rakeshadr commented on the issue:

https://github.com/apache/zookeeper/pull/157
  
Thanks @revans2 for the useful results. I spend sometime going through the 
changes and looks good to me. @hanm, please go ahead with merging this to 
branch-3.4.


---
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_branch35_solaris - Build # 438 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch35_solaris/438/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 278 lines...]
[junit] 2017-02-14 16:15:19,308 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 6264
[junit] 2017-02-14 16:15:19,309 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 5
[junit] 2017-02-14 16:15:19,309 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testClientReconnect
[junit] 2017-02-14 16:15:19,309 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testClientReconnect
[junit] 2017-02-14 16:15:19,309 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testClientReconnect
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 9.863 sec
[junit] 2017-02-14 16:15:39,228 [myid:] - INFO  
[main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
[junit] Running org.apache.zookeeper.CustomHostProviderTest
[junit] 2017-02-14 16:15:39,963 [myid:] - INFO  
[main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
[junit] 2017-02-14 16:15:40,679 [myid:] - INFO  [main:ZKTestCase$1@55] - 
STARTING testZooKeeperWithCustomHostProvider
[junit] 2017-02-14 16:15:40,682 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
testZooKeeperWithCustomHostProvider
[junit] 2017-02-14 16:15:40,720 [myid:] - INFO  [main:PortAssignment@157] - 
Single test process using ports from 11221 - 32767.
[junit] 2017-02-14 16:15:40,812 [myid:] - INFO  [main:PortAssignment@85] - 
Assigned port 11222 from range 11221 - 32767.
[junit] 2017-02-14 16:15:40,954 [myid:] - INFO  [main:Environment@109] - 
Client environment:zookeeper.version=3.5.3-alpha-SNAPSHOT--1, built on 
02/14/2017 16:12 GMT
[junit] 2017-02-14 16:15:40,954 [myid:] - INFO  [main:Environment@109] - 
Client environment:host.name=hudson-solaris
[junit] 2017-02-14 16:15:40,955 [myid:] - INFO  [main:Environment@109] - 
Client environment:java.version=1.7.0_79
[junit] 2017-02-14 16:15:40,955 [myid:] - INFO  [main:Environment@109] - 
Client environment:java.vendor=Oracle Corporation
[junit] 2017-02-14 16:15:40,955 [myid:] - INFO  [main:Environment@109] - 
Client 
environment:java.home=/zonestorage/hudson_solaris/home/hudson/tools/java/jdk1.7.0_79/jre
[junit] 2017-02-14 16:15:40,955 [myid:] - INFO  [main:Environment@109] - 
Client 

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

2017-02-14 Thread Patrick Hunt (JIRA)

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

Patrick Hunt commented on ZOOKEEPER-2693:
-

I had another thought on how to handle this - rather than on/off we could limit 
the number of 4lw that would be allowed to run in parallel. For example we 
could allow only a single 4lw to run at any one time. This would still provide 
the ability to run a 4lw, but with protection against overuse. It seems like 
this should be fairly simple to implement. Additionally we could provide this 
as an option (e.g. some folks might want to allow 5 to run in parallel). 
Regardless if we take this approach I think we would still want the on/off 
switches I already detailed.

> 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
>Priority: Blocker
> Fix For: 3.4.10, 3.5.3
>
>
> 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_branch34_openjdk7 - Build # 1391 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1391/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-5 (Ubuntu yahoo-not-h2 ubuntu ubuntu5 docker) in 
workspace /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7
Cloning the remote Git repository
Cloning repository git://git.apache.org/zookeeper.git
 > git init /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7 # 
 > timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
No valid HEAD. Skipping the resetting
 > git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git -c core.askpass=true 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 e8247eec1103e387e02bbb1e8859b4d468688f48 
(refs/remotes/origin/branch-3.4)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e8247eec1103e387e02bbb1e8859b4d468688f48
 > git rev-list e8247eec1103e387e02bbb1e8859b4d468688f48 # timeout=10
No emails were triggered.
[ZooKeeper_branch34_openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant 
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml 
-Djavac.target=1.7 clean test-core-java
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:442)
at java.net.URLClassLoader.access$100(URLClassLoader.java:64)
at java.net.URLClassLoader$1.run(URLClassLoader.java:354)
at java.net.URLClassLoader$1.run(URLClassLoader.java:348)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:347)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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_solaris - Build # 1472 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1472/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 125231 lines...]
[junit] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
[junit] at 
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
[junit] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
[junit] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
[junit] at java.net.Socket.connect(Socket.java:529)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:562)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumCnxManager.toSend(QuorumCnxManager.java:538)
[junit] at 
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.process(FastLeaderElection.java:452)
[junit] at 
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.run(FastLeaderElection.java:433)
[junit] at java.lang.Thread.run(Thread.java:662)
[junit] 2017-02-14 14:09:38,389 [myid:] - INFO  
[WorkerSender[myid=5]:QuorumPeer$QuorumServer@163] - Resolved hostname: 
127.0.0.1 to address: /127.0.0.1
[junit] 2017-02-14 14:09:38,391 [myid:] - WARN  
[QuorumPeer[myid=5]0.0.0.0/0.0.0.0:11237:QuorumPeer@910] - Unexpected exception
[junit] java.lang.InterruptedException
[junit] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:1961)
[junit] at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2038)
[junit] at 
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:424)
[junit] at 
org.apache.zookeeper.server.quorum.FastLeaderElection.lookForLeader(FastLeaderElection.java:832)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:908)
[junit] 2017-02-14 14:09:38,393 [myid:] - WARN  
[QuorumPeer[myid=5]0.0.0.0/0.0.0.0:11237:QuorumPeer@960] - QuorumPeer main 
thread exited
[junit] 2017-02-14 14:09:38,391 [myid:] - ERROR 
[/127.0.0.1:12242:QuorumCnxManager$Listener@763] - Exception while listening
[junit] java.net.SocketException: Socket closed
[junit] at java.net.PlainSocketImpl.socketAccept(Native Method)
[junit] at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
[junit] at java.net.ServerSocket.implAccept(ServerSocket.java:462)
[junit] at java.net.ServerSocket.accept(ServerSocket.java:430)
[junit] at 
org.apache.zookeeper.server.quorum.QuorumCnxManager$Listener.run(QuorumCnxManager.java:744)
[junit] 2017-02-14 14:09:38,394 [myid:] - INFO  [main:QuorumBase@310] - 
Shutting down leader election QuorumPeer[myid=5]0.0.0.0/0.0.0.0:11237
[junit] 2017-02-14 14:09:38,608 [myid:] - INFO  [main:QuorumBase@315] - 
Waiting for QuorumPeer[myid=5]0.0.0.0/0.0.0.0:11237 to exit thread
[junit] 2017-02-14 14:09:38,608 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11233
[junit] 2017-02-14 14:09:38,608 [myid:] - INFO  [main:QuorumBase@291] - 
127.0.0.1:11233 is no longer accepting client connections
[junit] 2017-02-14 14:09:38,609 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11234
[junit] 2017-02-14 14:09:38,609 [myid:] - INFO  [main:QuorumBase@291] - 
127.0.0.1:11234 is no longer accepting client connections
[junit] 2017-02-14 14:09:38,609 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11235
[junit] 2017-02-14 14:09:38,609 [myid:] - INFO  [main:QuorumBase@291] - 
127.0.0.1:11235 is no longer accepting client connections
[junit] 2017-02-14 14:09:38,609 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11236
[junit] 2017-02-14 14:09:38,609 [myid:] - INFO  [main:QuorumBase@291] - 
127.0.0.1:11236 is no longer accepting client connections
[junit] 2017-02-14 14:09:38,609 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11237
[junit] 2017-02-14 14:09:38,610 [myid:] - INFO  [main:QuorumBase@291] - 
127.0.0.1:11237 is no longer accepting client connections
[junit] 2017-02-14 14:09:38,611 [myid:] - INFO  
[/127.0.0.1:12238:QuorumCnxManager$Listener@776] - Leaving listener
[junit] 2017-02-14 14:09:38,611 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 118134
[junit] 2017-02-14 14:09:38,612 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 23
[junit] 2017-02-14 14:09:38,612 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD 
testObserversHammer
[junit] 2017-02-14 14:09:38,612 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED 

RE: ZooKeeper clients does not handle new error codes properly

2017-02-14 Thread Mohammad arshad
Created ZOOKEEPER-2695 to handle this scenario by throwing 
KeeperException.SystemErrorException instead of IllegalArgumentException

Best Regards
Mohammad Arshad
HUAWEI TECHNOLOGIES CO.LTD.
Huawei Tecnologies India Pvt. Ltd.
Near EPIP Industrial Area, Kundalahalli Village
Whitefield, Bangalore-560066
www.huawei.com
-
This e-mail and its attachments contain confidential information from HUAWEI, 
which 
is intended only for the person or entity whose address is listed above. Any 
use of the 
information contained herein in any way (including, but not limited to, total 
or partial 
disclosure, reproduction, or dissemination) by persons other than the intended 
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender by 
phone or email immediately and delete it!

-Original Message-
From: Mohammad arshad 
Sent: 05 October 2016 19:34
To: dev@zookeeper.apache.org; UserZooKeeper
Subject: RE: ZooKeeper clients does not handle new error codes properly

Thanks Michael Han for the information.
It is the same place in my case as well.

-Original Message-
From: Michael Han [mailto:h...@cloudera.com]
Sent: 04 October 2016 23:08
To: UserZooKeeper
Cc: dev@zookeeper.apache.org
Subject: Re: ZooKeeper clients does not handle new error codes properly

Hi Arshad,

I am curious where the IllegalArgumentException was thrown in code in your use 
case - I am asking because I spotted that in KeeperException.create, we have a 
default fall through [1] that throws IllegalArgumentException, and if this is 
not the place where you observed the IllegalArgumentException in your upgrade 
use case, then we may also need think to change the default fall through here 
from throwing IllegalArgumentException to return something like 
SystemErrorException, because it seems possible that unknown / not mapped error 
codes can be passed to KeeperException.create that will lead to 
IllegalArgumentException that client can't handle well?

[1] https://github.com/apache/zookeeper/blob/master/src/
java/main/org/apache/zookeeper/KeeperException.java#L144

On Tue, Oct 4, 2016 at 8:21 AM, Mohammad arshad 
wrote:

> Thanks Benjamin Reed,
> Client protocol version is 0, it is not changed. Also there is no 
> logic executed at the server side based on the client protocol version.
> Increasing the client protocol version and converting the errors at 
> server may be the ideal and more precise solution but to handle it in 
> a generic way can we convert the unknown error to 
> KeeperException.SystemErrorException
> at client side? Do you foresee any problem in this solution?
>
> Thanks
> -Arshad
>
>
> -Original Message-
> From: Benjamin Reed [mailto:br...@apache.org]
> Sent: 04 October 2016 10:27
> To: u...@zookeeper.apache.org
> Cc: DevZooKeeper
> Subject: Re: ZooKeeper clients does not handle new error codes 
> properly
>
> did we bump the protocol version when we added the new errors? the 
> server could do the conversion when it responds to older clients.
>
> On Mon, Oct 3, 2016 at 3:05 AM, Flavio Junqueira  wrote:
>
> > Hi Arshad,
> >
> > It makes sense to me. What if we convert unknown server errors to 
> > KeeperException.SystemErrorException? This is a generic error and it 
> > extends KeeperException.
> >
> > I don't see it as a big issue to make this change, but others may 
> > feel differently. If we do it, then we will need a release note 
> > pointing out the change of behavior.
> >
> > -Flavio
> >
> > > On 03 Oct 2016, at 08:54, Mohammad arshad 
> > > 
> > wrote:
> > >
> > > Hi All,
> > > In Zookeeper rolling upgrade scenario where server is new but 
> > > client is
> > old, when sever sends error code which is not understood by a 
> > client, client throws IllegalArgumentException. Generally 
> > IllegalArgumentException is not handled by any of the ZK applications.
> > It is too generic. How to handle this scenario in ZK applications?
> > > My understanding is instead of throwing IllegalArgumentException 
> > > we
> > should throw a subclass of KeeperException, for example 
> > InvalidErrorCodeException, so that zk apps can take more specific action.
> > > Any thoughts?
> > >
> > > Thanks
> > > -Arshad
> > >
> >
> >
>



--
Cheers
Michael.


[jira] [Created] (ZOOKEEPER-2695) Handle unknown error for rolling upgrade old client new server scenario

2017-02-14 Thread Mohammad Arshad (JIRA)
Mohammad Arshad created ZOOKEEPER-2695:
--

 Summary: Handle unknown error for rolling upgrade old client new 
server scenario
 Key: ZOOKEEPER-2695
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2695
 Project: ZooKeeper
  Issue Type: Bug
  Components: java client
Reporter: Mohammad Arshad


In Zookeeper rolling upgrade scenario where server is new but client is old, 
when sever sends error code which is not understood by the client, client 
throws IllegalArgumentException. Generally IllegalArgumentException is not 
handled by any of the ZK applications. 

KeeperException.SystemErrorException should be thrown instead of 
IllegalArgumentException





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


[jira] [Created] (ZOOKEEPER-2694) sync CLI command does not wait for result from server

2017-02-14 Thread Mohammad Arshad (JIRA)
Mohammad Arshad created ZOOKEEPER-2694:
--

 Summary: sync CLI command does not wait for result from server
 Key: ZOOKEEPER-2694
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2694
 Project: ZooKeeper
  Issue Type: Bug
  Components: java client
Reporter: Mohammad Arshad


sync CLI command does not wait for result from server. It returns immediately 
after invoking the sync's asynchronous API.
Executing bellow command does not give the expected result
 {{/bin/zkCli.sh -server host:port sync /}}



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


ZooKeeper-trunk-jdk8 - Build # 942 - Failure

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/942/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 496125 lines...]
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2017-02-14 12:00:33,628 [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-02-14 12:00:33,628 [myid:127.0.0.1:24687] - WARN  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1235] - Session 
0x253fc1e87 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-02-14 12:00:33,704 [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-02-14 12:00:33,704 [myid:127.0.0.1:24687] - WARN  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1235] - Session 
0x253fc1e870001 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-02-14 12:00:34,984 [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-02-14 12:00:34,984 [myid:127.0.0.1:24687] - WARN  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1235] - Session 
0x253fc1e87 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-02-14 12:00:35,486 [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-02-14 12:00:35,486 [myid:127.0.0.1:24687] - WARN  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1235] - Session 
0x253fc1e870001 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-02-14 12:00:37,038 [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-02-14 12:00:37,038 [myid:127.0.0.1:24687] - WARN  
[main-SendThread(127.0.0.1:24687):ClientCnxn$SendThread@1235] - Session 
0x253fc1e87 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 

ZooKeeper_branch35_openjdk7 - Build # 416 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/416/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-us1 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_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
Fetching upstream changes from git://git.apache.org/zookeeper.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch-3.5^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.5^{commit} # timeout=10
Checking out Revision 0816970930bb9565f13d310a1f55636e62cdfd19 
(refs/remotes/origin/branch-3.5)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0816970930bb9565f13d310a1f55636e62cdfd19
 > git rev-list 0816970930bb9565f13d310a1f55636e62cdfd19 # timeout=10
No emails were triggered.
[ZooKeeper_branch35_openjdk7] $ /home/jenkins/tools/ant/latest/bin/ant 
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml 
-Djavac.target=1.7 clean test-core-java
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: Test reports were found 
but none of them are new. Did tests run? 
For example, 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/build/test/logs/TEST-org.apache.jute.BinaryInputArchiveTest.xml
 is 1 day 23 hr old

Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

[jira] [Commented] (ZOOKEEPER-2687) Deadlock while shutting down the Leader server.

2017-02-14 Thread Mohammad Arshad (JIRA)

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

Mohammad Arshad commented on ZOOKEEPER-2687:


[~rakeshr] can you please have a look on the proposed change as you are most 
familiar with the related defect ZOOKEEPER-2380.

> Deadlock while shutting down the Leader server.
> ---
>
> Key: ZOOKEEPER-2687
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2687
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.5.2, 3.6.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2687-01.patch
>
>
> Leader server enters into deadlock while shutting down. This happens some 
> time only.
> The reason and deadlock flow is same as ZOOKEEPER-2380.
> shutdown was removed from synchronized block in ZOOKEEPER-2380
> Now shutdown is called from synchronized block from another place.
> {code}
> // check leader running status
> if (!this.isRunning()) {
> shutdown("Unexpected internal error");
> return;
> }
> {code}



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


ZooKeeper_branch35_jdk7 - Build # 850 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/850/

###
## LAST 60 LINES OF THE CONSOLE 
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-1 (ubuntu) in workspace 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7
 > 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 -c core.askpass=true fetch --tags --progress 
 > git://git.apache.org/zookeeper.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/branch-3.5^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/branch-3.5^{commit} # timeout=10
Checking out Revision 0816970930bb9565f13d310a1f55636e62cdfd19 
(refs/remotes/origin/branch-3.5)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0816970930bb9565f13d310a1f55636e62cdfd19
 > git rev-list 0816970930bb9565f13d310a1f55636e62cdfd19 # timeout=10
No emails were triggered.
[ZooKeeper_branch35_jdk7] $ /home/jenkins/tools/ant/latest/bin/ant 
-Dtest.output=yes -Dtest.junit.threads=8 -Dtest.junit.output.format=xml 
-Djavac.target=1.7 clean test-core-java
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
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-trunk-solaris - Build # 1506 - Still Failing

2017-02-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1506/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 473737 lines...]
[junit] 2017-02-14 08:25:17,261 [myid:] - INFO  [main:ClientBase@376] - 
STARTING server instance 127.0.0.1:11222
[junit] 2017-02-14 08:25:17,261 [myid:] - INFO  [main:ZooKeeperServer@908] 
- minSessionTimeout set to 6000
[junit] 2017-02-14 08:25:17,261 [myid:] - INFO  [main:ZooKeeperServer@917] 
- maxSessionTimeout set to 6
[junit] 2017-02-14 08:25:17,262 [myid:] - INFO  [main:ZooKeeperServer@160] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test7540179695344657669.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test7540179695344657669.junit.dir/version-2
[junit] 2017-02-14 08:25:17,262 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test7540179695344657669.junit.dir/version-2/snapshot.b
[junit] 2017-02-14 08:25:17,265 [myid:] - INFO  [main:FileTxnSnapLog@346] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test7540179695344657669.junit.dir/version-2/snapshot.b
[junit] 2017-02-14 08:25:17,266 [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-02-14 08:25:17,266 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2017-02-14 08:25:17,267 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:56485
[junit] 2017-02-14 08:25:17,269 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:56485
[junit] 2017-02-14 08:25:17,269 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2017-02-14 08:25:17,269 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@614] - Closed socket connection for client 
/127.0.0.1:56485 (no session established for client)
[junit] 2017-02-14 08:25:17,270 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2017-02-14 08:25:17,273 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2017-02-14 08:25:17,274 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2017-02-14 08:25:17,274 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2017-02-14 08:25:17,274 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2017-02-14 08:25:17,274 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17904
[junit] 2017-02-14 08:25:17,274 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2017-02-14 08:25:17,275 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2017-02-14 08:25:17,275 [myid:] - INFO  [main:ClientBase@558] - 
tearDown starting
[junit] 2017-02-14 08:25:17,352 [myid:] - INFO  [main:ZooKeeper@1324] - 
Session: 0x126b8b2b4cf closed
[junit] 2017-02-14 08:25:17,352 [myid:] - INFO  [main:ClientBase@528] - 
STOPPING server
[junit] 2017-02-14 08:25:17,352 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x126b8b2b4cf
[junit] 2017-02-14 08:25:17,353 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2017-02-14 08:25:17,353 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2017-02-14 08:25:17,353 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2017-02-14 08:25:17,353 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2017-02-14 08:25:17,353 [myid:] - INFO  [main:ZooKeeperServer@542] 
- shutting down
[junit] 2017-02-14 08:25:17,353 [myid:] - ERROR [main:ZooKeeperServer@506] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on