Build failed in Hudson: ZooKeeper-trunk #146
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/146/changes -- [...truncated 40272 lines...] [junit] 2008-11-17 11:25:09,386 - WARN [NIOServerCxn.Factory:33221:[EMAIL PROTECTED] - Connected to /127.0.0.1:39089 lastZxid 5 [junit] 2008-11-17 11:25:09,386 - WARN [NIOServerCxn.Factory:33221:[EMAIL PROTECTED] - Finished init of 0x11daa32487a: true [junit] 2008-11-17 11:25:09,387 - WARN [NIOServerCxn.Factory:33221:[EMAIL PROTECTED] - Renewing session 0x11daa32487a [junit] 2008-11-17 11:25:09,414 - WARN [main-SendThread:[EMAIL PROTECTED] - We are triggering an exists watch for delete! Shouldn't happen! [junit] 2008-11-17 11:25:09,416 - INFO [main:[EMAIL PROTECTED] - STOPPING server [junit] 2008-11-17 11:25:09,417 - WARN [main-SendThread:[EMAIL PROTECTED] - Exception closing session 0x11daa32487a to [EMAIL PROTECTED] [junit] java.io.IOException: Read error rc = -1 java.nio.DirectByteBuffer[pos=0 lim=4 cap=4] [junit] at org.apache.zookeeper.ClientCnxn$SendThread.doIO(ClientCnxn.java:608) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:838) [junit] 2008-11-17 11:25:09,418 - ERROR [NIOServerCxn.Factory:33221:[EMAIL PROTECTED] - = Goodbye cruel world == [junit] 2008-11-17 11:25:09,418 - INFO [main:[EMAIL PROTECTED] - shutdown of request processor complete [junit] 2008-11-17 11:25:09,525 - INFO [main:[EMAIL PROTECTED] - STARTING server [junit] 2008-11-17 11:25:09,526 - INFO [main:[EMAIL PROTECTED] - Created server [junit] 2008-11-17 11:25:09,528 - INFO [main:[EMAIL PROTECTED] - Reading snapshot /zonestorage/hudson/home/hudson/hudson/jobs/ZooKeeper-trunk/workspace/trunk/build/test/tmp/test21327.junit.dir/version-2/snapshot.5 [junit] 2008-11-17 11:25:09,530 - INFO [main:[EMAIL PROTECTED] - Snapshotting: 6 [junit] 2008-11-17 11:25:11,215 - INFO [main-SendThread:[EMAIL PROTECTED] - Attempting connection to server /127.0.0.1:33221 [junit] 2008-11-17 11:25:11,215 - INFO [main-SendThread:[EMAIL PROTECTED] - Priming connection to java.nio.channels.SocketChannel[connected local=/127.0.0.1:39094 remote=/127.0.0.1:33221] [junit] 2008-11-17 11:25:11,216 - WARN [NIOServerCxn.Factory:33221:[EMAIL PROTECTED] - Connected to /127.0.0.1:39094 lastZxid 6 [junit] 2008-11-17 11:25:11,217 - WARN [NIOServerCxn.Factory:33221:[EMAIL PROTECTED] - Finished init of 0x11daa32487a: true [junit] 2008-11-17 11:25:11,217 - WARN [NIOServerCxn.Factory:33221:[EMAIL PROTECTED] - Renewing session 0x11daa32487a [junit] 2008-11-17 11:25:11,276 - WARN [main-SendThread:[EMAIL PROTECTED] - We are triggering an exists watch for delete! Shouldn't happen! [junit] 2008-11-17 11:25:12,305 - INFO [main:[EMAIL PROTECTED] - Closing session: 0x11daa32487a [junit] 2008-11-17 11:25:12,305 - INFO [main:[EMAIL PROTECTED] - Closing ClientCnxn for session: 0x11daa32487a [junit] 2008-11-17 11:25:12,306 - INFO [ProcessThread:0:[EMAIL PROTECTED] - Processed session termination request for id: 0x11daa32487a [junit] 2008-11-17 11:25:12,313 - INFO [main-SendThread:[EMAIL PROTECTED] - Exception while closing send thread for session 0x11daa32487a : Read error rc = -1 java.nio.DirectByteBuffer[pos=0 lim=4 cap=4] [junit] 2008-11-17 11:25:12,415 - INFO [main:[EMAIL PROTECTED] - Disconnecting ClientCnxn for session: 0x11daa32487a [junit] 2008-11-17 11:25:12,415 - INFO [main:[EMAIL PROTECTED] - Session: 0x11daa32487a closed [junit] 2008-11-17 11:25:12,416 - INFO [main:[EMAIL PROTECTED] - tearDown starting [junit] 2008-11-17 11:25:12,416 - INFO [main-EventThread:[EMAIL PROTECTED] - EventThread shut down [junit] 2008-11-17 11:25:12,417 - ERROR [NIOServerCxn.Factory:33221:[EMAIL PROTECTED] - = Goodbye cruel world == [junit] 2008-11-17 11:25:12,417 - INFO [main:[EMAIL PROTECTED] - shutdown of request processor complete [junit] 2008-11-17 11:25:12,419 - INFO [main:[EMAIL PROTECTED] - FINISHED testWatcherAutoResetWithGlobal [junit] 2008-11-17 11:25:12,420 - INFO [main:[EMAIL PROTECTED] - STARTING testWatcherAutoResetWithLocal [junit] 2008-11-17 11:25:12,421 - INFO [main:[EMAIL PROTECTED] - Created server [junit] 2008-11-17 11:25:12,422 - INFO [main:[EMAIL PROTECTED] - Snapshotting: 0 [junit] 2008-11-17 11:25:12,424 - INFO [main:[EMAIL PROTECTED] - Client test setup finished [junit] 2008-11-17 11:25:12,425 - INFO [main-SendThread:[EMAIL PROTECTED] - Attempting connection to server /127.0.0.1:33221 [junit] 2008-11-17 11:25:12,426 - INFO [main-SendThread:[EMAIL PROTECTED] - Priming connection to java.nio.channels.SocketChannel[connected local=/127.0.0.1:39097 remote=/127.0.0.1:33221] [junit] 2008-11-17 11:25:12,426 - WARN [NIOServerCxn.Factory:33221:[EMAIL PROTECTED] - Connected to /127.0.0.1:39097 lastZxid 0 [junit]
[jira] Commented: (ZOOKEEPER-223) default log4j root logger configuration has neg perf impact with no benefit, change default level to INFO
[ https://issues.apache.org/jira/browse/ZOOKEEPER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648181#action_12648181 ] Mahadev konar commented on ZOOKEEPER-223: - +1 for the patch... default log4j root logger configuration has neg perf impact with no benefit, change default level to INFO - Key: ZOOKEEPER-223 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-223 Project: Zookeeper Issue Type: Improvement Components: java client, server Affects Versions: 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Fix For: 3.0.1, 3.1.0 Attachments: ZOOKEEPER-223.patch The default log4j.properties has: log4j.rootLogger=DEBUG, CONSOLE where the console appender is only outputting INFO level and above. This is resulting in a large number of debug logs being generated, which are all filtered out by the console appender (by default there are no other appenders used) We need to change the default rootLogger to INFO level, which will resolve this issue. Users are free to change this of course -- most likely they would only do this when debugging an issue, and would not want to run in DEBUG in production (again, they are free to choose). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-223) default log4j root logger configuration has neg perf impact with no benefit, change default level to INFO
[ https://issues.apache.org/jira/browse/ZOOKEEPER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-223: Resolution: Fixed Fix Version/s: (was: 3.0.1) Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) i just committed this. thanks pat. default log4j root logger configuration has neg perf impact with no benefit, change default level to INFO - Key: ZOOKEEPER-223 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-223 Project: Zookeeper Issue Type: Improvement Components: java client, server Affects Versions: 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Fix For: 3.1.0 Attachments: ZOOKEEPER-223.patch The default log4j.properties has: log4j.rootLogger=DEBUG, CONSOLE where the console appender is only outputting INFO level and above. This is resulting in a large number of debug logs being generated, which are all filtered out by the console appender (by default there are no other appenders used) We need to change the default rootLogger to INFO level, which will resolve this issue. Users are free to change this of course -- most likely they would only do this when debugging an issue, and would not want to run in DEBUG in production (again, they are free to choose). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-217) Errors in config file
[ https://issues.apache.org/jira/browse/ZOOKEEPER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar reassigned ZOOKEEPER-217: --- Assignee: Mahadev konar Errors in config file - Key: ZOOKEEPER-217 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-217 Project: Zookeeper Issue Type: Improvement Components: server Affects Versions: 3.0.0 Reporter: Flavio Paiva Junqueira Assignee: Mahadev konar Priority: Minor Fix For: 3.0.1 Attachments: ZOOKEEPER-217.patch Discussing 209 with Ben today, we thought that it would be better to have the parse method of QuorumPeerConfig returning a boolean that indicates whether the configuration is good or not, and let the caller decide whether to exit or not. Currently we execute a System.exit() on QuorumPeerConfig.parse when we have a critical configuration error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-217) Errors in config file
[ https://issues.apache.org/jira/browse/ZOOKEEPER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-217: Fix Version/s: (was: 3.1.0) 3.0.1 Status: Patch Available (was: Open) Errors in config file - Key: ZOOKEEPER-217 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-217 Project: Zookeeper Issue Type: Improvement Components: server Affects Versions: 3.0.0 Reporter: Flavio Paiva Junqueira Assignee: Mahadev konar Priority: Minor Fix For: 3.0.1 Attachments: ZOOKEEPER-217.patch Discussing 209 with Ben today, we thought that it would be better to have the parse method of QuorumPeerConfig returning a boolean that indicates whether the configuration is good or not, and let the caller decide whether to exit or not. Currently we execute a System.exit() on QuorumPeerConfig.parse when we have a critical configuration error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-217) Errors in config file
[ https://issues.apache.org/jira/browse/ZOOKEEPER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-217: Attachment: ZOOKEEPER-217.patch this patch fixes the issue and throws Illegalarugmentexcpetion that is caught in main and then exit() is called. This patch also includes the fix for ZOOKEEPER-209. Errors in config file - Key: ZOOKEEPER-217 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-217 Project: Zookeeper Issue Type: Improvement Components: server Affects Versions: 3.0.0 Reporter: Flavio Paiva Junqueira Priority: Minor Fix For: 3.0.1 Attachments: ZOOKEEPER-217.patch Discussing 209 with Ben today, we thought that it would be better to have the parse method of QuorumPeerConfig returning a boolean that indicates whether the configuration is good or not, and let the caller decide whether to exit or not. Currently we execute a System.exit() on QuorumPeerConfig.parse when we have a critical configuration error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-209) nullpointerexception if election port is not specified.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-209: Status: Open (was: Patch Available) cancelling this patch.. since its fixed in ZOOKEEPER-217. nullpointerexception if election port is not specified. --- Key: ZOOKEEPER-209 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-209 Project: Zookeeper Issue Type: Bug Affects Versions: 3.0.0 Reporter: Mahadev konar Assignee: Flavio Paiva Junqueira Fix For: 3.0.1, 3.1.0 Attachments: ZOOKEEPER-209.patch The quoruom servers throw a nullpointer exception and still keep running. We should atleast have a nice debug message and quit... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-213) programmer guide C api docs are out of sync with latest zookeeper.h
[ https://issues.apache.org/jira/browse/ZOOKEEPER-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-213: Hadoop Flags: [Reviewed] programmer guide C api docs are out of sync with latest zookeeper.h Key: ZOOKEEPER-213 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-213 Project: Zookeeper Issue Type: Bug Components: documentation Affects Versions: 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Fix For: 3.0.1, 3.1.0 Attachments: ZOOKEEPER-213.patch see http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#Zookeeper+C+client+API and compare with src/c/zookeeper.h -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-213) programmer guide C api docs are out of sync with latest zookeeper.h
[ https://issues.apache.org/jira/browse/ZOOKEEPER-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-213: Resolution: Fixed Status: Resolved (was: Patch Available) committed in trunk to revision 718440 and in 3.0 to revision 718441. thanks pat. programmer guide C api docs are out of sync with latest zookeeper.h Key: ZOOKEEPER-213 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-213 Project: Zookeeper Issue Type: Bug Components: documentation Affects Versions: 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Fix For: 3.0.1, 3.1.0 Attachments: ZOOKEEPER-213.patch see http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#Zookeeper+C+client+API and compare with src/c/zookeeper.h -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-206) documentation tab should contain the version number (and other small site changes)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-206: --- Fix Version/s: 3.0.1 Assignee: Patrick Hunt Status: Patch Available (was: Open) documentation tab should contain the version number (and other small site changes) --- Key: ZOOKEEPER-206 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-206 Project: Zookeeper Issue Type: Bug Components: documentation Affects Versions: 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.0.1, 3.1.0 Attachments: ZOOKEEPER-206_301.patch, ZOOKEEPER-206_trunk.patch Feedback from Doug Cutting on 3.0.0 documentation: - The Zookeeper Documentation tab should contain the version number. - Informal Documentation might better be named Other Documentation. - The Other Info page should be removed, since it contains nothing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-219) events.poll timeout in watcher test too short
[ https://issues.apache.org/jira/browse/ZOOKEEPER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648424#action_12648424 ] Mahadev konar commented on ZOOKEEPER-219: - +1 for the patch ... the tests pass events.poll timeout in watcher test too short - Key: ZOOKEEPER-219 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-219 Project: Zookeeper Issue Type: Bug Affects Versions: 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.0.1, 3.1.0 Attachments: ZOOKEEPER-219.patch in watchertest there are some event.poll calls that have 1milli timeouts e = localWatcher.events.poll(1, TimeUnit.MILLISECONDS); this is showing falure in some cases under hudson (I assume when it's under load from other tests running for other proj) We should review the poll calls and verify adequate timeouts. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository
Deploy ZooKeeper 3.0.0 to a Maven Repository Key: ZOOKEEPER-224 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 Project: Zookeeper Issue Type: Task Components: build Affects Versions: 3.0.0 Reporter: Hiram Chirino Priority: Critical I've created the maven poms needed for the 3.0.0 release. The directory structure and artifacts located at: http://people.apache.org/~chirino/zk-repo/ aka people.apache.org:/x1/users/chirino/public_html/zk-repo Just need sto get GPG signed by the project KEY and deployed to: people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Maven artifacts for 3.0.0 release
I created issue: https://issues.apache.org/jira/browse/ZOOKEEPER-224 to track the request. Who's the current ZooKeeper release manager? On Fri, Nov 14, 2008 at 11:07 AM, Hiram Chirino [EMAIL PROTECTED] wrote: Hi Guys, I've create a small maven 2 repository for the ZooKeeper 3.0.0 release at: http://people.apache.org/~chirino/zk-repo/ Ideally the ZooKeeper PMC can review the artifacts validate that they match the release, GPG sign all the poms and jars and push them out to the main apache m2 maven repository so it can get synchronized into the maven central repo. That's at people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository BTW. But For now maven users of ZooKeeper can add the following to their build to automatically download the release: repositories repository idchirino-zk-repo/id namePrivate ZooKeeper Repo/name urlhttp://people.apache.org/~chirino/zk-repo//url /repository /repositories dependencies dependency groupIdorg.apache.hadoop.zookeeper/groupId artifactIdzookeeper/artifactId version3.0.0/version /dependency /dependencies -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository
[ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648447#action_12648447 ] Patrick Hunt commented on ZOOKEEPER-224: Hey there, I'm the current release manager (phunt). Deploy ZooKeeper 3.0.0 to a Maven Repository Key: ZOOKEEPER-224 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 Project: Zookeeper Issue Type: Task Components: build Affects Versions: 3.0.0 Reporter: Hiram Chirino Priority: Critical I've created the maven poms needed for the 3.0.0 release. The directory structure and artifacts located at: http://people.apache.org/~chirino/zk-repo/ aka people.apache.org:/x1/users/chirino/public_html/zk-repo Just need sto get GPG signed by the project KEY and deployed to: people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
