ZooKeeper_branch34 - Build # 1437 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 207675 lines...]
[junit] 2015-12-09 10:22:10,591 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2015-12-09 10:22:10,591 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2015-12-09 10:22:10,593 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2015-12-09 10:22:10,594 [myid:] - INFO  [main:ZooKeeperServer@467] 
- shutting down
[junit] 2015-12-09 10:22:10,594 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2015-12-09 10:22:10,594 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2015-12-09 10:22:10,594 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2015-12-09 10:22:10,594 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2015-12-09 10:22:10,595 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2015-12-09 10:22:10,596 [myid:] - INFO  
[main:FinalRequestProcessor@415] - shutdown of request processor complete
[junit] 2015-12-09 10:22:10,597 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-09 10:22:10,598 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2015-12-09 10:22:10,600 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2015-12-09 10:22:10,600 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2015-12-09 10:22:10,601 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2015-12-09 10:22:10,601 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2015-12-09 10:22:10,602 [myid:] - INFO  [main:ZooKeeperServer@168] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/branch-3.4/build/test/tmp/test66151354228964998.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/branch-3.4/build/test/tmp/test66151354228964998.junit.dir/version-2
[junit] 2015-12-09 10:22:10,620 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-09 10:22:10,622 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:60867
[junit] 2015-12-09 10:22:10,622 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:60867
[junit] 2015-12-09 10:22:10,623 [myid:] - INFO  
[Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2015-12-09 10:22:10,625 [myid:] - INFO  
[Thread-5:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:60867 (no session established for client)
[junit] 2015-12-09 10:22:10,625 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2015-12-09 10:22:10,628 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2015-12-09 10:22:10,630 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2015-12-09 10:22:10,630 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2015-12-09 10:22:10,630 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2015-12-09 10:22:10,631 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 31173
[junit] 2015-12-09 10:22:10,631 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 21
[junit] 2015-12-09 10:22:10,631 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2015-12-09 10:22:10,633 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2015-12-09 10:22:10,645 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15186433568 closed
[junit] 2015-12-09 10:22:10,645 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2015-12-09 10:22:10,647 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2015-12-09 10:22:10,647 [myid:] - INFO  [main:ZooKeeperServer@467] 
- shutting down
[junit] 2015-12-09 10:22:10,647 [myid:] - INFO  

[jira] [Updated] (ZOOKEEPER-2336) Jenkins not working due to old SVN

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2336:

Assignee: Akihiro Suda

> Jenkins not working due to old SVN
> --
>
> Key: ZOOKEEPER-2336
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2336
> Project: ZooKeeper
>  Issue Type: Test
>  Components: build
>Reporter: Akihiro Suda
>Assignee: Akihiro Suda
> Attachments: ZOOKEEPER-2336-v1.patch
>
>
> Jenkins seems not working since Build #2976 (Dec 6, 2015) due to SVN.
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2976/console
> {panel}
>  [exec] svn: E155036: Please see the 'svn upgrade' command
>  [exec] svn: E155036: The working copy at 
> '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk'
>  [exec] is too old (format 10) to work with client version '1.8.8 
> (r1568071)' (expects format 31). You need to upgrade the working copy first.
>  [exec] 
> {panel}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34_jdk7 - Build # 1005 - Failure

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 217851 lines...]
[junit] 2015-12-09 09:41:59,600 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2015-12-09 09:41:59,600 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2015-12-09 09:41:59,600 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2015-12-09 09:41:59,601 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2015-12-09 09:41:59,601 [myid:] - INFO  
[main:FinalRequestProcessor@415] - shutdown of request processor complete
[junit] 2015-12-09 09:41:59,602 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-09 09:41:59,603 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2015-12-09 09:41:59,604 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2015-12-09 09:41:59,604 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2015-12-09 09:41:59,605 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2015-12-09 09:41:59,605 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2015-12-09 09:41:59,606 [myid:] - INFO  [main:ZooKeeperServer@168] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test7740143133282773240.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test7740143133282773240.junit.dir/version-2
[junit] 2015-12-09 09:41:59,610 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-09 09:41:59,611 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:42036
[junit] 2015-12-09 09:41:59,611 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:42036
[junit] 2015-12-09 09:41:59,612 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2015-12-09 09:41:59,612 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:42036 (no session established for client)
[junit] 2015-12-09 09:41:59,613 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2015-12-09 09:41:59,615 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2015-12-09 09:41:59,615 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2015-12-09 09:41:59,616 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2015-12-09 09:41:59,616 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2015-12-09 09:41:59,616 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32616
[junit] 2015-12-09 09:41:59,616 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2015-12-09 09:41:59,617 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2015-12-09 09:41:59,617 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2015-12-09 09:41:59,681 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x151861e6b94 closed
[junit] 2015-12-09 09:41:59,682 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2015-12-09 09:41:59,682 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x151861e6b94
[junit] 2015-12-09 09:41:59,682 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2015-12-09 09:41:59,682 [myid:] - INFO  [main:ZooKeeperServer@467] 
- shutting down
[junit] 2015-12-09 09:41:59,683 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2015-12-09 09:41:59,683 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2015-12-09 09:41:59,683 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2015-12-09 09:41:59,683 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2015-12-09 09:41:59,684 [myid:] - INFO  

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: .htaccess)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: aspxshell.aspx, don.cer, simo.asp, uss.php.hack
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: index.php
index.htm

test2

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: index.htm, index.php, up.php
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: simo.asp
don.cer
aspxshell.aspx
uss.php.hack

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: aspxshell.aspx, don.cer, simo.asp, uss.php.hack
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: up.php)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: aspxshell.aspx, don.cer, simo.asp, uss.php.hack
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: simo.asp)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) alert('XSSED BY BLACKANONYMFOX')

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Summary: alert('XSSED BY BLACKANONYMFOX')  (was: JMX is 
disabled even if JMXDISABLE is false)

> alert('XSSED BY BLACKANONYMFOX')
> -
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Summary: JMX is disabled even if JMXDISABLE is false  (was: 
alert('XSSED BY BLACKANONYMFOX'))

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: .htaccess

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: .htaccess, index.htm, index.php, up.php
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: index.php)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: index.php

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: up.php.png

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: up.php.png
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: don.cer)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: up.php

test

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: up.php
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Comment: was deleted

(was: test)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: .htaccess, index.htm, index.php, up.php
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Comment: was deleted

(was: test2)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: .htaccess, index.htm, index.php, up.php
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Comment: was deleted

(was: alert('XSSED BY BLACKANONYMFOX'))

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: .htaccess, index.htm, index.php, up.php
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: OK Bye.png

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: OK Bye.png
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin commented on ZOOKEEPER-2340:
--

alert('XSSED BY BLACKANONYMFOX')

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: aspxshell.aspx)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: up.php.png)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: index.htm)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: aspxshell.aspx, don.cer, simo.asp, uss.php.hack
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: index.php)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: aspxshell.aspx, don.cer, simo.asp, uss.php.hack
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: OK Bye.png)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: index.php

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: index.php
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: index.jpg

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: index.jpg, up.jpg
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: uss.php.hack)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Comment: was deleted

(was: A comment with security level 'jira-users' was removed.)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: .png)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: index.jpg)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: uss.php.hack
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: uss.php.hack

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: uss.php.hack
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: up.jpg)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: uss.php.hack
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: up.jpg

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: up.jpg
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: (was: uss.php.hack)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: aspxshell.aspx, don.cer, simo.asp
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[admin (JIRA)]

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

admin updated ZOOKEEPER-2340:
-
Attachment: .png

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: .png
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: index.php)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: up.jpg)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Blocked user

[Flavio Junqueira]

I'm sorry about the spam coming from JIRA ZK-2340, but there was someone 
posting arbitrary files (they looked malicious, but frankly I didn't dig any 
deeper). I asked INFRA to block the user, which they did (INFRA-10927 
).

Thanks,
-Flavio

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: up.php)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-235) SSL Support for clients

[Jason Rosenberg (JIRA)]

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

Jason Rosenberg commented on ZOOKEEPER-235:
---

Is this still an issue, now that client-server ssl is now supported (over 
netty) in 3.5.1-alpha?

> SSL Support for clients
> ---
>
> Key: ZOOKEEPER-235
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-235
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: c client, java client, server
>Reporter: Benjamin Reed
>Priority: Minor
>
> ZooKeeper should be able to support SSL for ZooKeeper clients. As part of the 
> implementation we should also add an X509AuthenticationProvider so that 
> client side certifications can be used for authentication.
> The tricky part of the implementation will be integrating with the 
> non-blocking NIO calls that we use. There are various web pages that describe 
> how to do it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-2340:

Attachment: (was: index.txt)

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-1029) C client bug in zookeeper_init (if bad hostname is given)

[Flavio Junqueira (JIRA)]

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

Flavio Junqueira updated ZOOKEEPER-1029:

Attachment: ZOOKEEPER-1029-3.5.patch

[~cnauroth] could you have a look at this, please? this is the version for 3.5 
and trunk of the patch so that we can close this issue.

> C client bug in zookeeper_init (if bad hostname is given)
> -
>
> Key: ZOOKEEPER-1029
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1029
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.3.2, 3.4.6, 3.5.0
>Reporter: Dheeraj Agrawal
>Assignee: Flavio Junqueira
>Priority: Blocker
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.4.patch, 
> ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.4.patch, 
> ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.5.patch
>
>
> If you give invalid hostname to zookeeper_init method, it's not able to 
> resolve it, and it tries to do the cleanup (free buffer/completion lists/etc) 
> . The adaptor_init() is not called for this code path, so the lock,cond 
> variables (for adaptor, completion lists) are not initialized.
> As part of the cleanup it's trying to clean up some buffers and acquires 
> locks and unlocks (where the locks have not yet been initialized, so 
> unlocking fails) 
> lock_completion_list(>sent_requests); - pthread_mutex/cond not 
> initialized
> tmp_list = zh->sent_requests;
> zh->sent_requests.head = 0;
> zh->sent_requests.last = 0;
> unlock_completion_list(>sent_requests);   trying to broadcast here 
> on uninitialized cond
> It should do error checking to see if locking succeeds before unlocking it. 
> If Locking fails, then appropriate error handling has to be done.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2281) ZK Server startup fails if there are spaces in the JAVA_HOME path

[Chris Nauroth (JIRA)]

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

Chris Nauroth commented on ZOOKEEPER-2281:
--

The same patch applies cleanly to branch-3.4.  I just retested with a build 
from branch-3.4, and the patch worked fine.  [~rgs], may I commit this to 
branch-3.4 for inclusion in the future 3.4.8 release?

> ZK Server startup fails if there are spaces in the JAVA_HOME path
> -
>
> Key: ZOOKEEPER-2281
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2281
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
> Environment: Windows
>Reporter: neha
>Assignee: neha
>Priority: Minor
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2281-00.patch, ZOOKEEPER-2281-01.patch, 
> ZOOKEEPER-2281-02.patch
>
>
> Zookeeper startup fails if there are spaces in the %JAVA_HOME% variable. 
> {code}
> if not exist %JAVA_HOME%\bin\java.exe (
>   echo Error: JAVA_HOME is incorrectly set.
>   goto :eof
> )
> set JAVA=%JAVA_HOME%\bin\java
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1460) IPv6 literal address not supported for quorum members

[Chris Nauroth (JIRA)]

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

Chris Nauroth commented on ZOOKEEPER-1460:
--

[~rgs] and [~rakeshr], since we've shipped 3.4.7, do you mind if I commit this 
to branch-3.4 now?

> IPv6 literal address not supported for quorum members
> -
>
> Key: ZOOKEEPER-1460
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1460
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum
>Affects Versions: 3.4.3
>Reporter: Chris Dolan
>Assignee: Joseph Walton
> Fix For: 3.5.2, 3.6.0
>
> Attachments: 
> ZOOKEEPER-1460-accept-square-bracket-delimited-IPv6-literals.2.diff, 
> ZOOKEEPER-1460-accept-square-bracket-delimited-IPv6-literals.diff, 
> ZOOKEEPER-1460-for-3.5.0.patch, ZOOKEEPER-1460.003.patch
>
>
> Via code inspection, I see that the "server.nnn" configuration key does not 
> support literal IPv6 addresses because the property value is split on ":". In 
> v3.4.3, the problem is in QuorumPeerConfig:
> {noformat}
> String parts[] = value.split(":");
> InetSocketAddress addr = new InetSocketAddress(parts[0],
> Integer.parseInt(parts[1]));
> {noformat}
> In the current trunk 
> (http://svn.apache.org/viewvc/zookeeper/trunk/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java?view=markup)
>  this code has been refactored into QuorumPeer.QuorumServer, but the bug 
> remains:
> {noformat}
> String serverClientParts[] = addressStr.split(";");
> String serverParts[] = serverClientParts[0].split(":");
> addr = new InetSocketAddress(serverParts[0],
> Integer.parseInt(serverParts[1]));
> {noformat}
> This bug probably affects very few users because most will naturally use a 
> hostname rather than a literal IP address. But given that IPv6 addresses are 
> supported for clients via ZOOKEEPER-667 it seems that server support should 
> be fixed too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ZOOKEEPER-2341) bin/zkEnv.cmd needs quotes around %JAVA%

[Karl Mortensen (JIRA)]

Karl Mortensen created ZOOKEEPER-2341:
-

 Summary: bin/zkEnv.cmd needs quotes around %JAVA%
 Key: ZOOKEEPER-2341
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2341
 Project: ZooKeeper
  Issue Type: Bug
Affects Versions: 3.4.6
Reporter: Karl Mortensen
Priority: Trivial


I just downloaded ZooKeeper 3.4.7 (wouldn't let me put that version in the 
"Affects Version/s" field) and it doesn't work out of the box on Windows 7, 
which is brutal for folks who don't understand.

It complains that you don't have JAVA_HOME set right if you have it set to a 
path with spaces e.g. C:\program files\java\blah will fail.

All the following need quotes around and %VARIABLE% expansions to deal with 
potential spaces in the path:

* bin/zkCli.cmd
* bin/zkEnv.cmd
* bin/zkServer.cmd
 
Should be a trivial fix.

Definition of Done:
zkCli.cmd, zkEnv.cmd and zkServer.cm work out of the box on Windows 7.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Adding a new API to ZooKeeper 3.4? (ZOOKEEPER-1962/ZOOKEEPER-2260)

[Chris Nauroth]

Hello Tim,

Thank you for expressing interest in contributing this code!  We have a
wiki page that describes the contribution process [1].  We track all work
using JIRA, so the first step would be to create a JIRA describing what
you are proposing to contribute.

I think we'll need to decide how your work relates to the existing native
CLI already in the ZooKeeper codebase [2].  Would you consider adapting
your work onto that existing CLI, or do you think it would have to be
essentially a rewrite?  If the latter, then we'd probably need to give
some consideration to the switch to C++.  The current native CLI is C.  I
don't think there is existing precedent for C++ in ZooKeeper, except for
contrib modules.  I think we'll want to avoid a situation where there are
multiple native CLIs shipping in ZooKeeper, in addition to the Java one.

The first step is definitely a JIRA though.  Technical details like this
would get discussed there, and the JIRA would serve as a record of the
community's decisions.

[1] https://wiki.apache.org/hadoop/ZooKeeper/HowToContribute

[2] https://github.com/apache/zookeeper/blob/trunk/src/c/src/cli.c

--Chris Nauroth




On 12/8/15, 6:58 PM, "Crowder Tim"  wrote:

>Tangentially related question...
>
>I have a C++ cli for zookeeper modeled after unix shell.
>It has ls (with lots of options including recursive, long, and ACL
>listing),
>cp, touch, cat, etc. And command/filename completion and history.
>
>I've secured permission from work (Yahoo) to contribute it.
>How do I go about submitting it?
>
>Thanks!
>
>.timrc
>
>
>On Tue, 12/8/15, Chris Nauroth  wrote:
>
> Subject: Re: Adding a new API to ZooKeeper 3.4?
>(ZOOKEEPER-1962/ZOOKEEPER-2260)
> To: "dev@zookeeper.apache.org" 
> Date: Tuesday, December 8, 2015, 4:24 PM
> 
> Thanks for the response,
> Patrick.  Considering that, it sounds like
> recursive ls is a non-starter for 3.4, but we
> can focus on shipping it in
> 3.5.  I'll
> focus on that in the code reviews.
> 
> --Chris Nauroth
> 
> 
> 
> 
> On
> 12/8/15, 4:12 PM, "Patrick Hunt" 
> wrote:
> 
> >On Tue, Dec 8,
> 2015 at 3:01 PM, Chris Nauroth 
> >wrote:
> >> Do we have
> any kind of policy regarding adding new public APIs in
> the
> >>3.4 stable maintenance
> release?  Adding a new API won't harm
> >>backwards-compatibility, but it does
> mean that an upgraded client can't
> >>use the new API until the server side
> gets upgraded too.  I'd expect
> >>adding a new API is overall OK, subject
> to standard risk assessment for
> >>any
> patch going into a stable maintenance line.
> >>
> >
> >Hi Chris. It's always been the case
> that we only allow fixes in fix
> >releases. Things like API changes are
> always introduced in minor
> >releases, and
> they need to be backward compatible. Major releases are
> >for cases where we need to break b/w compat
> (which hasn't happened
> >since we
> moved to Apache).
> >
> >Patrick
> >
> >> ZOOKEEPER-1962 proposes enhancing the
> CLI to support recursively
> >>listing
> children.  However, running this on a large tree would
> risk
> >>hitting the jute.maxBuffer
> threshold, consuming a lot of memory, and
> >>consuming a thread for a long time to
> process the request.  I'd like to
> >>propose that ZOOKEEPER-2260 (paginated
> getChildren) be a pre-requisite
> >>for
> the CLI enhancement, so that we can avoid these problems.
> However,
> >>I'd also like us to try
> to ship the feature in a future 3.4 release,
> >>because it's very useful for
> operators.  This is the main motivation for
> >>my policy question about adding new
> APIs in a stable line.
> >>
> >> --Chris Nauroth
> >
>

[jira] [Commented] (ZOOKEEPER-2229) Several four-letter words are undocumented.

[Chris Nauroth (JIRA)]

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

Chris Nauroth commented on ZOOKEEPER-2229:
--

Hi [~rgs].  Now that we've shipped 3.4.7, do you mind if I commit this to 
branch-3.4?

> Several four-letter words are undocumented.
> ---
>
> Key: ZOOKEEPER-2229
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2229
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2229.001.patch, ZOOKEEPER-2229.002.patch
>
>
> The {{isro}}, {{gtmk}} and {{stmk}} commands are not covered in the 
> four-letter word documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1029) C client bug in zookeeper_init (if bad hostname is given)

[Hadoop QA (JIRA)]

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

Hadoop QA commented on ZOOKEEPER-1029:
--

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12776638/ZOOKEEPER-1029-3.5.patch
  against trunk revision 1718758.

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

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 findbugs.  The patch does not introduce any new Findbugs (version 2.0.3) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

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

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

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2992//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2992//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2992//console

This message is automatically generated.

> C client bug in zookeeper_init (if bad hostname is given)
> -
>
> Key: ZOOKEEPER-1029
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1029
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.3.2, 3.4.6, 3.5.0
>Reporter: Dheeraj Agrawal
>Assignee: Flavio Junqueira
>Priority: Blocker
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.4.patch, 
> ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.4.patch, 
> ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.5.patch
>
>
> If you give invalid hostname to zookeeper_init method, it's not able to 
> resolve it, and it tries to do the cleanup (free buffer/completion lists/etc) 
> . The adaptor_init() is not called for this code path, so the lock,cond 
> variables (for adaptor, completion lists) are not initialized.
> As part of the cleanup it's trying to clean up some buffers and acquires 
> locks and unlocks (where the locks have not yet been initialized, so 
> unlocking fails) 
> lock_completion_list(>sent_requests); - pthread_mutex/cond not 
> initialized
> tmp_list = zh->sent_requests;
> zh->sent_requests.head = 0;
> zh->sent_requests.last = 0;
> unlock_completion_list(>sent_requests);   trying to broadcast here 
> on uninitialized cond
> It should do error checking to see if locking succeeds before unlocking it. 
> If Locking fails, then appropriate error handling has to be done.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-1029 PreCommit Build #2992

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1029
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2992/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 385005 lines...]
 [exec] -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
 [exec] Please justify why no new tests are needed 
for this patch.
 [exec] Also please list what manual steps were 
performed to verify this patch.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 2.0.3) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2992//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2992//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2992//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] 2ccc9ad421b20dce73c4c36595dafbd96c303686 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1827:
 exec returned: 1

Total time: 18 minutes 23 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-1029
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



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

[jira] [Reopened] (ZOOKEEPER-2281) ZK Server startup fails if there are spaces in the JAVA_HOME path

[Chris Nauroth (JIRA)]

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

Chris Nauroth reopened ZOOKEEPER-2281:
--

I'm reopening this for consideration of a backport to the 3.4 line.

> ZK Server startup fails if there are spaces in the JAVA_HOME path
> -
>
> Key: ZOOKEEPER-2281
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2281
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
> Environment: Windows
>Reporter: neha
>Assignee: neha
>Priority: Minor
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2281-00.patch, ZOOKEEPER-2281-01.patch, 
> ZOOKEEPER-2281-02.patch
>
>
> Zookeeper startup fails if there are spaces in the %JAVA_HOME% variable. 
> {code}
> if not exist %JAVA_HOME%\bin\java.exe (
>   echo Error: JAVA_HOME is incorrectly set.
>   goto :eof
> )
> set JAVA=%JAVA_HOME%\bin\java
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2281) ZK Server startup fails if there are spaces in the JAVA_HOME path

[Chris Nauroth (JIRA)]

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

Chris Nauroth updated ZOOKEEPER-2281:
-
Fix Version/s: 3.4.8

> ZK Server startup fails if there are spaces in the JAVA_HOME path
> -
>
> Key: ZOOKEEPER-2281
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2281
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
> Environment: Windows
>Reporter: neha
>Assignee: neha
>Priority: Minor
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2281-00.patch, ZOOKEEPER-2281-01.patch, 
> ZOOKEEPER-2281-02.patch
>
>
> Zookeeper startup fails if there are spaces in the %JAVA_HOME% variable. 
> {code}
> if not exist %JAVA_HOME%\bin\java.exe (
>   echo Error: JAVA_HOME is incorrectly set.
>   goto :eof
> )
> set JAVA=%JAVA_HOME%\bin\java
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ZOOKEEPER-2341) bin/zkEnv.cmd needs quotes around %JAVA%

[Chris Nauroth (JIRA)]

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

Chris Nauroth resolved ZOOKEEPER-2341.
--
Resolution: Duplicate

Hi [~kmorten...@basistech.com].  Thank you for the bug report.  We fixed this 
for the upcoming 3.5.2-alpha release.  This was tracked in issue 
ZOOKEEPER-2281.  However, we did not backport the fix to the 3.4 maintenance 
line.  I just reopened that issue so that we can consider it for ZooKeeper 
3.4.8.  I'm going to resolve this one as a duplicate.  I recommend adding 
yourself as a watcher on ZOOKEEPER-2281 if you'd like further updates.

> bin/zkEnv.cmd needs quotes around %JAVA%
> 
>
> Key: ZOOKEEPER-2341
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2341
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Karl Mortensen
>Priority: Trivial
>
> I just downloaded ZooKeeper 3.4.7 (wouldn't let me put that version in the 
> "Affects Version/s" field) and it doesn't work out of the box on Windows 7, 
> which is brutal for folks who don't understand.
> It complains that you don't have JAVA_HOME set right if you have it set to a 
> path with spaces e.g. C:\program files\java\blah will fail.
> All the following need quotes around and %VARIABLE% expansions to deal with 
> potential spaces in the path:
> * bin/zkCli.cmd
> * bin/zkEnv.cmd
> * bin/zkServer.cmd
>  
> Should be a trivial fix.
> Definition of Done:
> zkCli.cmd, zkEnv.cmd and zkServer.cm work out of the box on Windows 7.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2281) ZK Server startup fails if there are spaces in the JAVA_HOME path

[Raul Gutierrez Segales (JIRA)]

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

Raul Gutierrez Segales commented on ZOOKEEPER-2281:
---

[~cnauroth]: definitely. 

> ZK Server startup fails if there are spaces in the JAVA_HOME path
> -
>
> Key: ZOOKEEPER-2281
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2281
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
> Environment: Windows
>Reporter: neha
>Assignee: neha
>Priority: Minor
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2281-00.patch, ZOOKEEPER-2281-01.patch, 
> ZOOKEEPER-2281-02.patch
>
>
> Zookeeper startup fails if there are spaces in the %JAVA_HOME% variable. 
> {code}
> if not exist %JAVA_HOME%\bin\java.exe (
>   echo Error: JAVA_HOME is incorrectly set.
>   goto :eof
> )
> set JAVA=%JAVA_HOME%\bin\java
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

[Chris Nauroth (JIRA)]

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

Chris Nauroth commented on ZOOKEEPER-2342:
--

I've confirmed that the problem was introduced by ZOOKEEPER-1371, which 
corresponds to git commit hash 4be4adfa32dc0bae0736ee1d6c04cb4cfc2d13a4.  If I 
check out the commit right before that, then the problem no longer repros.

> ZooKeeper cannot write logs, because there is no SLF4J binding available on 
> the runtime classpath.
> --
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
> this also removed the Log4J SLF4J binding jar from the runtime classpath.  
> Without any SLF4J binding jar available on the runtime classpath, the it is 
> impossible to write logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1371) Remove dependency on log4j in the source code.

[Chris Nauroth (JIRA)]

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

Chris Nauroth commented on ZOOKEEPER-1371:
--

After this patch, ZooKeeper no longer produces any logging, because there is no 
SLF4J binding jar available on the runtime classpath.  I filed blocker issue 
ZOOKEEPER-2342 for follow-up.

> Remove dependency on log4j in the source code.
> --
>
> Key: ZOOKEEPER-1371
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1371
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.4.0, 3.4.1, 3.4.2, 3.4.3
>Reporter: Mahadev konar
>Assignee: Arshad Mohammad
>  Labels: patch
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1371-05.patch, ZOOKEEPER-1371.patch, 
> ZOOKEEPER-1371.patch, ZOOKEEPER-1371.patch, ZOOKEEPER-1371.patch
>
>
> ZOOKEEPER-850 added slf4j to ZK. We still depend on log4j in our codebase. We 
> should remove the dependency on log4j so that we can make logging pluggable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

[Chris Nauroth (JIRA)]

Chris Nauroth created ZOOKEEPER-2342:


 Summary: ZooKeeper cannot write logs, because there is no SLF4J 
binding available on the runtime classpath.
 Key: ZOOKEEPER-2342
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Chris Nauroth
Priority: Blocker
 Fix For: 3.5.2, 3.6.0


ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
this also removed the Log4J SLF4J binding jar from the runtime classpath.  
Without any SLF4J binding jar available on the runtime classpath, the it is 
impossible to write logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34 - Build # 1438 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 202305 lines...]
[junit] 2015-12-10 02:22:48,515 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2015-12-10 02:22:48,515 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2015-12-10 02:22:48,516 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2015-12-10 02:22:48,517 [myid:] - INFO  [main:ZooKeeperServer@467] 
- shutting down
[junit] 2015-12-10 02:22:48,517 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2015-12-10 02:22:48,517 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2015-12-10 02:22:48,517 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2015-12-10 02:22:48,518 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2015-12-10 02:22:48,519 [myid:] - INFO  
[main:FinalRequestProcessor@415] - shutdown of request processor complete
[junit] 2015-12-10 02:22:48,520 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-10 02:22:48,521 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2015-12-10 02:22:48,523 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2015-12-10 02:22:48,524 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2015-12-10 02:22:48,525 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2015-12-10 02:22:48,525 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2015-12-10 02:22:48,526 [myid:] - INFO  [main:ZooKeeperServer@168] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/branch-3.4/build/test/tmp/test4605442115247721615.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/branch-3.4/build/test/tmp/test4605442115247721615.junit.dir/version-2
[junit] 2015-12-10 02:22:48,527 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2015-12-10 02:22:48,532 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-10 02:22:48,533 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:53369
[junit] 2015-12-10 02:22:48,533 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:53369
[junit] 2015-12-10 02:22:48,538 [myid:] - INFO  
[Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2015-12-10 02:22:48,538 [myid:] - INFO  
[Thread-5:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:53369 (no session established for client)
[junit] 2015-12-10 02:22:48,538 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2015-12-10 02:22:48,540 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2015-12-10 02:22:48,541 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2015-12-10 02:22:48,541 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2015-12-10 02:22:48,541 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2015-12-10 02:22:48,542 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 31191
[junit] 2015-12-10 02:22:48,542 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 21
[junit] 2015-12-10 02:22:48,542 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2015-12-10 02:22:48,543 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2015-12-10 02:22:48,589 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15189b2b147 closed
[junit] 2015-12-10 02:22:48,589 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2015-12-10 02:22:48,590 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2015-12-10 02:22:48,590 [myid:] - INFO  [main:ZooKeeperServer@467] 
- shutting down
[junit] 2015-12-10 02:22:48,590 [myid:] - INFO  

[jira] [Commented] (ZOOKEEPER-2252) Random test case failure in org.apache.zookeeper.test.StaticHostProviderTest

[Raul Gutierrez Segales (JIRA)]

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

Raul Gutierrez Segales commented on ZOOKEEPER-2252:
---

[~cnauroth]: lgtm, please apply. Thanks!

> Random test case failure in org.apache.zookeeper.test.StaticHostProviderTest
> 
>
> Key: ZOOKEEPER-2252
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2252
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZK-2252-try-repro-on-jenkins.patch, 
> ZOOKEEPER-2252-02.patch, ZOOKEEPER-2252-03.patch, ZOOKEEPER-2252-04.patch, 
> ZOOKEEPER-2252-05.patch, ZOOKEEPER-2252-06.patch
>
>
> Test 
> {{org.apache.zookeeper.test.StaticHostProviderTest.testTwoInvalidHostAddresses()}}
>  fails randomly.
> Refer bellow test ci buils:
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2827/testReport/
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2828/testReport/
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2830/testReport/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2252) Random test case failure in org.apache.zookeeper.test.StaticHostProviderTest

[Chris Nauroth (JIRA)]

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

Chris Nauroth commented on ZOOKEEPER-2252:
--

The test failure was in TestReconfig.cc.  This has been a flaky test, so the 
failure is unrelated to this patch.

I don't understand why this reported a release audit warning.  The patch 
doesn't create any new files that need a license header applied.  The audit 
output file is missing from Jenkins.  This can't be related to the patch.  I 
ran the release audit check locally, and it was fine.

I will wait until Thursday, 12/10, to commit this, in case [~rgs] or any other 
committers would like to review.

> Random test case failure in org.apache.zookeeper.test.StaticHostProviderTest
> 
>
> Key: ZOOKEEPER-2252
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2252
> Project: ZooKeeper
>  Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Arshad Mohammad
>Assignee: Arshad Mohammad
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZK-2252-try-repro-on-jenkins.patch, 
> ZOOKEEPER-2252-02.patch, ZOOKEEPER-2252-03.patch, ZOOKEEPER-2252-04.patch, 
> ZOOKEEPER-2252-05.patch, ZOOKEEPER-2252-06.patch
>
>
> Test 
> {{org.apache.zookeeper.test.StaticHostProviderTest.testTwoInvalidHostAddresses()}}
>  fails randomly.
> Refer bellow test ci buils:
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2827/testReport/
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2828/testReport/
> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2830/testReport/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

[Chris Nauroth (JIRA)]

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

Chris Nauroth commented on ZOOKEEPER-2342:
--

To reproduce the issue, run {{ant clean tar}} on the tip of current trunk, 
unpack the distro, copy zoo_sample.cfg to zoo.cfg, and then run it.  Both 
{{zkServer.sh start-foreground}} and {{zkCli.sh}} will show this error:

{code}
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
{code}

There will be no additional logging after that.

> ZooKeeper cannot write logs, because there is no SLF4J binding available on 
> the runtime classpath.
> --
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
> this also removed the Log4J SLF4J binding jar from the runtime classpath.  
> Without any SLF4J binding jar available on the runtime classpath, the it is 
> impossible to write logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ZOOKEEPER-2281) ZK Server startup fails if there are spaces in the JAVA_HOME path

[Chris Nauroth (JIRA)]

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

Chris Nauroth resolved ZOOKEEPER-2281.
--
Resolution: Fixed

Thank you, Raul!  I committed this to branch-3.4, and I'm resolving the issue 
again.

> ZK Server startup fails if there are spaces in the JAVA_HOME path
> -
>
> Key: ZOOKEEPER-2281
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2281
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
> Environment: Windows
>Reporter: neha
>Assignee: neha
>Priority: Minor
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2281-00.patch, ZOOKEEPER-2281-01.patch, 
> ZOOKEEPER-2281-02.patch
>
>
> Zookeeper startup fails if there are spaces in the %JAVA_HOME% variable. 
> {code}
> if not exist %JAVA_HOME%\bin\java.exe (
>   echo Error: JAVA_HOME is incorrectly set.
>   goto :eof
> )
> set JAVA=%JAVA_HOME%\bin\java
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-2340 PreCommit Build #2993

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2993/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 19 lines...]
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
Buildfile: 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml

check-for-findbugs:

findbugs.check:

forrest.check:

hudson-test-patch:
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Testing patch for ZOOKEEPER-2340.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Updating '.':
 [exec] At revision 1719013.
 [exec] ZOOKEEPER-2340 is not "Patch Available".  Exiting.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD SUCCESSFUL
Total time: 12 seconds
Archiving artifacts
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Recording test results
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
ERROR: Publisher 'Publish JUnit test result report' failed: No test report 
files were found. Configuration error?
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
[description-setter] Description set: ZOOKEEPER-2340
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7
Setting 
LATEST1_7_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.7



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

[jira] [Commented] (ZOOKEEPER-1962) Add a CLI command to recursively list a znode and children

[Raul Gutierrez Segales (JIRA)]

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

Raul Gutierrez Segales commented on ZOOKEEPER-1962:
---

[~busbey], [~ggop]: sorry for the delay in reviewing this - I'll look at it 
now. In the meanwhile, fwiw, zk-shell already supports this things (and other 
advanced commands) (and is available via pip install zk-shell): 
https://github.com/rgs1/zk_shell

> Add a CLI command to recursively list a znode and children
> --
>
> Key: ZOOKEEPER-1962
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1962
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: java client
>Affects Versions: 3.4.6
>Reporter: Gautam Gopalakrishnan
>Assignee: Gautam Gopalakrishnan
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1962.diff, ZOOKEEPER-1962_v2.patch, 
> ZOOKEEPER-1962_v3.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When troubleshooting applications where znodes can be multiple levels deep  
> (eg. HBase replication), it is handy to see all child znodes recursively 
> rather than run an ls for each node manually.
> So I propose adding an option to the "ls" command (-r) which will list all 
> child nodes under a given znode. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34_jdk7 - Build # 1006 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 210312 lines...]
[junit] 2015-12-10 03:56:34,265 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2015-12-10 03:56:34,265 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2015-12-10 03:56:34,268 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2015-12-10 03:56:34,269 [myid:] - INFO  
[main:FinalRequestProcessor@415] - shutdown of request processor complete
[junit] 2015-12-10 03:56:34,269 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-10 03:56:34,270 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2015-12-10 03:56:34,273 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2015-12-10 03:56:34,273 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2015-12-10 03:56:34,273 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2015-12-10 03:56:34,274 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2015-12-10 03:56:34,275 [myid:] - INFO  [main:ZooKeeperServer@168] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test6808488257920276981.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test6808488257920276981.junit.dir/version-2
[junit] 2015-12-10 03:56:34,265 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2015-12-10 03:56:34,282 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-10 03:56:34,284 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:36204
[junit] 2015-12-10 03:56:34,284 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:36204
[junit] 2015-12-10 03:56:34,285 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2015-12-10 03:56:34,285 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:36204 (no session established for client)
[junit] 2015-12-10 03:56:34,286 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2015-12-10 03:56:34,289 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2015-12-10 03:56:34,290 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2015-12-10 03:56:34,290 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2015-12-10 03:56:34,290 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2015-12-10 03:56:34,291 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32656
[junit] 2015-12-10 03:56:34,292 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 21
[junit] 2015-12-10 03:56:34,292 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2015-12-10 03:56:34,292 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2015-12-10 03:56:34,331 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x1518a08892c closed
[junit] 2015-12-10 03:56:34,331 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2015-12-10 03:56:34,332 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x1518a08892c
[junit] 2015-12-10 03:56:34,332 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2015-12-10 03:56:34,332 [myid:] - INFO  [main:ZooKeeperServer@467] 
- shutting down
[junit] 2015-12-10 03:56:34,332 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2015-12-10 03:56:34,333 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2015-12-10 03:56:34,333 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2015-12-10 03:56:34,334 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2015-12-10 03:56:34,334 [myid:] - INFO  
[main:FinalRequestProcessor@415] - 

[jira] [Commented] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Hudson (JIRA)]

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

Hudson commented on ZOOKEEPER-2340:
---

SUCCESS: Integrated in ZooKeeper-trunk #2826 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/2826/])
ZOOKEEPER-2340: JMX is disabled even if JMXDISABLE is false
(Arshad Mohammad via rgs) (rgs: 
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN=rev=1719011])
* trunk/CHANGES.txt
* trunk/bin/zkServer.sh


> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2340-01.patch
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1460) IPv6 literal address not supported for quorum members

[Raul Gutierrez Segales (JIRA)]

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

Raul Gutierrez Segales commented on ZOOKEEPER-1460:
---

[~cnauroth]: please go ahead - thanks!

> IPv6 literal address not supported for quorum members
> -
>
> Key: ZOOKEEPER-1460
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1460
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: quorum
>Affects Versions: 3.4.3
>Reporter: Chris Dolan
>Assignee: Joseph Walton
> Fix For: 3.5.2, 3.6.0
>
> Attachments: 
> ZOOKEEPER-1460-accept-square-bracket-delimited-IPv6-literals.2.diff, 
> ZOOKEEPER-1460-accept-square-bracket-delimited-IPv6-literals.diff, 
> ZOOKEEPER-1460-for-3.5.0.patch, ZOOKEEPER-1460.003.patch
>
>
> Via code inspection, I see that the "server.nnn" configuration key does not 
> support literal IPv6 addresses because the property value is split on ":". In 
> v3.4.3, the problem is in QuorumPeerConfig:
> {noformat}
> String parts[] = value.split(":");
> InetSocketAddress addr = new InetSocketAddress(parts[0],
> Integer.parseInt(parts[1]));
> {noformat}
> In the current trunk 
> (http://svn.apache.org/viewvc/zookeeper/trunk/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java?view=markup)
>  this code has been refactored into QuorumPeer.QuorumServer, but the bug 
> remains:
> {noformat}
> String serverClientParts[] = addressStr.split(";");
> String serverParts[] = serverClientParts[0].split(":");
> addr = new InetSocketAddress(serverParts[0],
> Integer.parseInt(serverParts[1]));
> {noformat}
> This bug probably affects very few users because most will naturally use a 
> hostname rather than a literal IP address. But given that IPv6 addresses are 
> supported for clients via ZOOKEEPER-667 it seems that server support should 
> be fixed too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

[Arshad Mohammad (JIRA)]

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

Arshad Mohammad commented on ZOOKEEPER-2342:


small correction: user should put slf4j-log4j12-1.7.5.jar and log4j-1.2.17.jar 
in /lib

> ZooKeeper cannot write logs, because there is no SLF4J binding available on 
> the runtime classpath.
> --
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
> this also removed the Log4J SLF4J binding jar from the runtime classpath.  
> Without any SLF4J binding jar available on the runtime classpath, the it is 
> impossible to write logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

[Arshad Mohammad (JIRA)]

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

Arshad Mohammad commented on ZOOKEEPER-2342:


Hi [~cnauroth], it is right that log4j dependency has been removed but this was 
the intention of the ZOOKEEPER-1371 jira.  May be we can document some where 
that users  have to put runtime library of the logging framework of their 
choice. For example to use log4j user should put slf4j-log4j12-1.7.5.jar and 
slf4j-log4j12-1.7.5.jar in /lib

> ZooKeeper cannot write logs, because there is no SLF4J binding available on 
> the runtime classpath.
> --
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
> this also removed the Log4J SLF4J binding jar from the runtime classpath.  
> Without any SLF4J binding jar available on the runtime classpath, the it is 
> impossible to write logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

[Arshad Mohammad (JIRA)]

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

Arshad Mohammad commented on ZOOKEEPER-2342:


small correction: user should put slf4j-log4j12-1.7.5.jar and log4j-1.2.17.jar 
in /lib

> ZooKeeper cannot write logs, because there is no SLF4J binding available on 
> the runtime classpath.
> --
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
> this also removed the Log4J SLF4J binding jar from the runtime classpath.  
> Without any SLF4J binding jar available on the runtime classpath, the it is 
> impossible to write logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-235) SSL Support for clients

[Raul Gutierrez Segales (JIRA)]

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

Raul Gutierrez Segales commented on ZOOKEEPER-235:
--

I think we should close it... [~hdeng]?

> SSL Support for clients
> ---
>
> Key: ZOOKEEPER-235
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-235
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: c client, java client, server
>Reporter: Benjamin Reed
>Priority: Minor
>
> ZooKeeper should be able to support SSL for ZooKeeper clients. As part of the 
> implementation we should also add an X509AuthenticationProvider so that 
> client side certifications can be used for authentication.
> The tricky part of the implementation will be integrating with the 
> non-blocking NIO calls that we use. There are various web pages that describe 
> how to do it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2260) Paginated getChildren call

[Raul Gutierrez Segales (JIRA)]

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

Raul Gutierrez Segales commented on ZOOKEEPER-2260:
---

[~mprime]: sorry for the delay in reviewing this - are you still working on 
this? Could you put the patch either in reviews.apache.org or on a branch on 
github (maybe better/easier) so that I can add some inline comments? Thanks!

 

> Paginated getChildren call
> --
>
> Key: ZOOKEEPER-2260
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2260
> Project: ZooKeeper
>  Issue Type: New Feature
>Affects Versions: 3.4.5, 3.4.6, 3.5.0, 4.0.0
>Reporter: Marco P.
>Priority: Minor
>  Labels: api, features
> Fix For: 4.0.0
>
> Attachments: ZOOKEEPER-2260.patch
>
>
> Add pagination support to the getChildren() call, allowing clients to iterate 
> over children N at the time.
> Motivations for this include:
>   - Getting out of a situation where so many children were created that 
> listing them exceeded the network buffer sizes (making it impossible to 
> recover by deleting)[1]
>  - More efficient traversal of nodes with large number of children [2]
> I do have a patch (for 3.4.6) we've been using successfully for a while, but 
> I suspect much more work is needed for this to be accepted. 
> [1] https://issues.apache.org/jira/browse/ZOOKEEPER-272
> [2] https://issues.apache.org/jira/browse/ZOOKEEPER-282



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

[Arshad Mohammad (JIRA)]

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

Arshad Mohammad updated ZOOKEEPER-2340:
---
Attachment: ZOOKEEPER-2340-01.patch

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: ZOOKEEPER-2340-01.patch
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2342) ZooKeeper cannot write logs, because there is no SLF4J binding available on the runtime classpath.

[Arshad Mohammad (JIRA)]

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

Arshad Mohammad commented on ZOOKEEPER-2342:


small correction: user should put slf4j-log4j12-1.7.5.jar and log4j-1.2.17.jar 
in /lib

> ZooKeeper cannot write logs, because there is no SLF4J binding available on 
> the runtime classpath.
> --
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Chris Nauroth
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that 
> this also removed the Log4J SLF4J binding jar from the runtime classpath.  
> Without any SLF4J binding jar available on the runtime classpath, the it is 
> impossible to write logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1029) C client bug in zookeeper_init (if bad hostname is given)

[Raul Gutierrez Segales (JIRA)]

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

Raul Gutierrez Segales commented on ZOOKEEPER-1029:
---

[~fpj]: a few comments:

* in lock_reconfig/unlock_reconfig and enter_critical/leave_critical if the the 
adaptor is not initialized we return 0 (lock or unlock succeeded) - is this 
actually desired? If so, maybe add a comment explaining why this is so?

* in:

{code}
-lock_completion_list(>sent_requests);
-tmp_list = zh->sent_requests;
-zh->sent_requests.head = 0;
-zh->sent_requests.last = 0;
-unlock_completion_list(>sent_requests);
-while (tmp_list.head) {


+if (lock_completion_list(>sent_requests) == 0) {
+tmp_list = zh->sent_requests;
+zh->sent_requests.head = 0;
+zh->sent_requests.last = 0;
+unlock_completion_list(>sent_requests);
+while (tmp_list.head) {
{code}

we are now iterating over tmp_list.head *only if* zh->requests was locked - do 
we need to couple them? Or should it be:

{code}
+if (lock_completion_list(>sent_requests) == 0) {
+tmp_list = zh->sent_requests;
+zh->sent_requests.head = 0;
+zh->sent_requests.last = 0;
+unlock_completion_list(>sent_requests);
+ }
+ while (tmp_list.head) {
+ ...
{code}

?

* similarly, in:

{code}
-a_list.completion = NULL;
-a_list.next = NULL;
-zoo_lock_auth(zh);
...
+if (zoo_lock_auth(zh) == 0) {
+a_list.completion = NULL;
+a_list.next = NULL;
+
+get_auth_completions(>auth_h, _list);
+zoo_unlock_auth(zh);
{code}

setting a_list.completion = NULL and a_list.next = NULL didn't previously 
depend on obtaining zoo_lock_auth.. but now they do. Again, should it just be:

{code}
+a_list.completion = NULL;
+a_list.next = NULL;
+if (zoo_lock_auth(zh) == 0) {
+get_auth_completions(>auth_h, _list);
+zoo_unlock_auth(zh);
+ }
{code}

?

> C client bug in zookeeper_init (if bad hostname is given)
> -
>
> Key: ZOOKEEPER-1029
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1029
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: c client
>Affects Versions: 3.3.2, 3.4.6, 3.5.0
>Reporter: Dheeraj Agrawal
>Assignee: Flavio Junqueira
>Priority: Blocker
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.4.patch, 
> ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.4.patch, 
> ZOOKEEPER-1029-3.4.patch, ZOOKEEPER-1029-3.5.patch
>
>
> If you give invalid hostname to zookeeper_init method, it's not able to 
> resolve it, and it tries to do the cleanup (free buffer/completion lists/etc) 
> . The adaptor_init() is not called for this code path, so the lock,cond 
> variables (for adaptor, completion lists) are not initialized.
> As part of the cleanup it's trying to clean up some buffers and acquires 
> locks and unlocks (where the locks have not yet been initialized, so 
> unlocking fails) 
> lock_completion_list(>sent_requests); - pthread_mutex/cond not 
> initialized
> tmp_list = zh->sent_requests;
> zh->sent_requests.head = 0;
> zh->sent_requests.last = 0;
> unlock_completion_list(>sent_requests);   trying to broadcast here 
> on uninitialized cond
> It should do error checking to see if locking succeeds before unlocking it. 
> If Locking fails, then appropriate error handling has to be done.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2229) Several four-letter words are undocumented.

[Raul Gutierrez Segales (JIRA)]

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

Raul Gutierrez Segales commented on ZOOKEEPER-2229:
---

[~cnauroth]: go for it (ditto for anything that's for 3.4.x). thanks!

> Several four-letter words are undocumented.
> ---
>
> Key: ZOOKEEPER-2229
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2229
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2229.001.patch, ZOOKEEPER-2229.002.patch
>
>
> The {{isro}}, {{gtmk}} and {{stmk}} commands are not covered in the 
> four-letter word documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1962) Add a CLI command to recursively list a znode and children

[Gautam Gopalakrishnan (JIRA)]

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

Gautam Gopalakrishnan commented on ZOOKEEPER-1962:
--

I'll submit a patch in the next day or two, sorry for the delay.

> Add a CLI command to recursively list a znode and children
> --
>
> Key: ZOOKEEPER-1962
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1962
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: java client
>Affects Versions: 3.4.6
>Reporter: Gautam Gopalakrishnan
>Assignee: Gautam Gopalakrishnan
>Priority: Minor
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-1962.diff, ZOOKEEPER-1962_v2.patch, 
> ZOOKEEPER-1962_v3.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When troubleshooting applications where znodes can be multiple levels deep  
> (eg. HBase replication), it is handy to see all child znodes recursively 
> rather than run an ls for each node manually.
> So I propose adding an option to the "ls" command (-r) which will list all 
> child nodes under a given znode. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2229) Several four-letter words are undocumented.

[Raul Gutierrez Segales (JIRA)]

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

Raul Gutierrez Segales commented on ZOOKEEPER-2229:
---

[~cnauroth]: oh, this is actually your code so you can't push it yourself.. 
i'll merge it. 

> Several four-letter words are undocumented.
> ---
>
> Key: ZOOKEEPER-2229
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2229
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: documentation
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2229.001.patch, ZOOKEEPER-2229.002.patch
>
>
> The {{isro}}, {{gtmk}} and {{stmk}} commands are not covered in the 
> four-letter word documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34_solaris - Build # 1072 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1072/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 177999 lines...]
[junit] 2015-12-10 06:50:06,741 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2015-12-10 06:50:06,741 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2015-12-10 06:50:06,742 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2015-12-10 06:50:06,742 [myid:] - INFO  [main:ZooKeeperServer@467] 
- shutting down
[junit] 2015-12-10 06:50:06,742 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2015-12-10 06:50:06,743 [myid:] - INFO  
[main:PrepRequestProcessor@767] - Shutting down
[junit] 2015-12-10 06:50:06,743 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2015-12-10 06:50:06,743 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2015-12-10 06:50:06,743 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2015-12-10 06:50:06,743 [myid:] - INFO  
[main:FinalRequestProcessor@415] - shutdown of request processor complete
[junit] 2015-12-10 06:50:06,744 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-10 06:50:06,744 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2015-12-10 06:50:06,745 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2015-12-10 06:50:06,745 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2015-12-10 06:50:06,745 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2015-12-10 06:50:06,745 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2015-12-10 06:50:06,746 [myid:] - INFO  [main:ZooKeeperServer@168] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test4625243351010699128.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test4625243351010699128.junit.dir/version-2
[junit] 2015-12-10 06:50:06,748 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2015-12-10 06:50:06,749 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:58467
[junit] 2015-12-10 06:50:06,749 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:58467
[junit] 2015-12-10 06:50:06,749 [myid:] - INFO  
[Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2015-12-10 06:50:06,749 [myid:] - INFO  
[Thread-5:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:58467 (no session established for client)
[junit] 2015-12-10 06:50:06,750 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2015-12-10 06:50:06,751 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2015-12-10 06:50:06,751 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2015-12-10 06:50:06,751 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2015-12-10 06:50:06,751 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2015-12-10 06:50:06,751 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 9033
[junit] 2015-12-10 06:50:06,752 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2015-12-10 06:50:06,752 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2015-12-10 06:50:06,752 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2015-12-10 06:50:06,832 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x1518aa76ae7 closed
[junit] 2015-12-10 06:50:06,832 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x1518aa76ae7
[junit] 2015-12-10 06:50:06,832 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2015-12-10 06:50:06,833 [myid:] - INFO  [main:ZooKeeperServer@467] 
- shutting down
[junit] 2015-12-10 06:50:06,833 [myid:] - INFO  
[main:SessionTrackerImpl@225] - 

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

['or''=' (JIRA)]

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

'or''=' updated ZOOKEEPER-2340:
---
Attachment: index.txt

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: index.txt
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2340) JMX is disabled even if JMXDISABLE is false

['or''=' (JIRA)]

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

'or''=' updated ZOOKEEPER-2340:
---
Attachment: up.php

> JMX is disabled even if JMXDISABLE is false
> ---
>
> Key: ZOOKEEPER-2340
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2340
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: neha
>Assignee: Arshad Mohammad
>Priority: Minor
> Attachments: index.txt, up.php
>
>
> Currently, to enable jmx for zookeeper, need to comment the property 
> JMXDISABLE as JMXDISABLE=false continues to disable JMX.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)