Build failed in Hudson: ZooKeeper-trunk #44
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/44/changes -- [...truncated 19841 lines...] [junit] 2008-08-05 10:43:59,392 - INFO [ProcessThread:[EMAIL PROTECTED] - Processed session termination request for id: 11b927727680001 [junit] 2008-08-05 10:43:59,403 - WARN [SendThread:[EMAIL PROTECTED] - Closing: [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:491) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:718) [junit] before shutdown zs! [junit] after shutdown zs! [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 16.911 sec [junit] Running org.apache.zookeeper.test.WatcherFuncTest [junit] 2008-08-05 10:44:01,024 - INFO [main:[EMAIL PROTECTED] - Client test setup [junit] 2008-08-05 10:44:06,370 - INFO [main:[EMAIL PROTECTED] - Client test setup finished [junit] 2008-08-05 10:44:06,389 - INFO [SendThread:[EMAIL PROTECTED] - Attempting connection to server /127.0.0.1:33221 [junit] 2008-08-05 10:44:06,390 - INFO [SendThread:[EMAIL PROTECTED] - Priming connection to java.nio.channels.SocketChannel[connected local=/127.0.0.1:49757 remote=/127.0.0.1:33221] [junit] 2008-08-05 10:44:06,401 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Connected to /127.0.0.1:49757 lastZxid 0 [junit] 2008-08-05 10:44:06,404 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Creating new session 11b92775ed1 [junit] 2008-08-05 10:44:06,589 - WARN [SyncThread:[EMAIL PROTECTED] - Finished init of 11b92775ed1: true [junit] 2008-08-05 10:44:06,592 - INFO [SendThread:[EMAIL PROTECTED] - Attempting connection to server /127.0.0.1:33221 [junit] 2008-08-05 10:44:06,593 - INFO [SendThread:[EMAIL PROTECTED] - Priming connection to java.nio.channels.SocketChannel[connected local=/127.0.0.1:49758 remote=/127.0.0.1:33221] [junit] 2008-08-05 10:44:06,594 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Connected to /127.0.0.1:49758 lastZxid 0 [junit] 2008-08-05 10:44:06,594 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Creating new session 11b92775ed10001 [junit] 2008-08-05 10:44:06,637 - WARN [SyncThread:[EMAIL PROTECTED] - Finished init of 11b92775ed10001: true [junit] 2008-08-05 10:44:06,833 - INFO [ProcessThread:[EMAIL PROTECTED] - Processed session termination request for id: 11b92775ed1 [junit] 2008-08-05 10:44:06,851 - WARN [SendThread:[EMAIL PROTECTED] - Closing: [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:491) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:718) [junit] 2008-08-05 10:44:06,961 - INFO [ProcessThread:[EMAIL PROTECTED] - Processed session termination request for id: 11b92775ed10001 [junit] 2008-08-05 10:44:06,992 - WARN [SendThread:[EMAIL PROTECTED] - Closing: [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:491) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:718) [junit] 2008-08-05 10:44:08,250 - INFO [SendThread:[EMAIL PROTECTED] - Attempting connection to server /127.0.0.1:33221 [junit] 2008-08-05 10:44:08,251 - INFO [SendThread:[EMAIL PROTECTED] - Priming connection to java.nio.channels.SocketChannel[connected local=/127.0.0.1:49760 remote=/127.0.0.1:33221] [junit] 2008-08-05 10:44:08,252 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Connected to /127.0.0.1:49760 lastZxid 10 [junit] 2008-08-05 10:44:08,253 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Finished init of 11b92775ed1: false [junit] 2008-08-05 10:44:08,253 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Renewing session 11b92775ed1 [junit] 2008-08-05 10:44:08,254 - WARN [SendThread:[EMAIL PROTECTED] - Closing: [junit] java.io.IOException: Session Expired [junit] at org.apache.zookeeper.ClientCnxn$SendThread.readConnectResult(ClientCnxn.java:414) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.doIO(ClientCnxn.java:499) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:718) [junit] 2008-08-05 10:44:12,110 - INFO [main:[EMAIL PROTECTED] - Clent test shutdown [junit] 2008-08-05 10:44:12,113 - ERROR [NIOServerCxn.Factory:[EMAIL PROTECTED] - = Goodbye cruel world == [junit] 2008-08-05 10:44:12,114 - INFO [main:[EMAIL PROTECTED] - Client test shutdown finished [junit] 2008-08-05 10:44:12,116 - INFO [main:[EMAIL PROTECTED] - Client test setup [junit] 2008-08-05 10:44:17,120 - INFO [main:[EMAIL PROTECTED] - Client
[jira] Resolved: (ZOOKEEPER-49) SetACL does not work
[
https://issues.apache.org/jira/browse/ZOOKEEPER-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Reed resolved ZOOKEEPER-49.
Resolution: Fixed
The patch for the dependent issue fixed this issue as well.
SetACL does not work
Key: ZOOKEEPER-49
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-49
Project: Zookeeper
Issue Type: Bug
Components: server
Reporter: Benjamin Reed
Assignee: Benjamin Reed
As reported by Shane:
Still exploring the ACL stuff in Zookeeper. Tried using setACL for a
path but get InvalidACL error thrown looking at pRequest in
PrepRequestProcessor ... and in particular these lines ...
SetACLRequest setAclRequest = new SetACLRequest();
if (!fixupACL(request.authInfo,
setAclRequest.getAcl())) {
throw new KeeperException(Code.InvalidACL);
}
a new SetACLRequest will return a null when called in fixupACL
returning false and throwing the exception as far as I can see.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-91) provide an option for the WriteLock to also watch the locks own znode, so that if someone else deletes it then it is equivalent to calling WriteLock.unlock()
[ https://issues.apache.org/jira/browse/ZOOKEEPER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12619882#action_12619882 ] Benjamin Reed commented on ZOOKEEPER-91: +1 provide an option for the WriteLock to also watch the locks own znode, so that if someone else deletes it then it is equivalent to calling WriteLock.unlock() - Key: ZOOKEEPER-91 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-91 Project: Zookeeper Issue Type: Sub-task Components: java client Reporter: james strachan Most clients probably wont need this, but it could be a handy system management feature to allow the WriteLock to watch its own znode so that if someone else deletes it, it then relinquishes the lock and tries to get it back again -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-103) Reorganize the ZooKeeper source distro to follow maven conventions
[ https://issues.apache.org/jira/browse/ZOOKEEPER-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12619975#action_12619975 ] Doug Cutting commented on ZOOKEEPER-103: On ZOOKEEPER-83 we plainly agreed that we were going to compromise and use maven conventions for the directory structure I don't see that. Pat Nigel agreed that we should be able to produce Maven artifacts. Mahadev supported Maven naming conventions, but I don't see Pat reversing his -1 on supporting multiple build systems. Reorganize the ZooKeeper source distro to follow maven conventions -- Key: ZOOKEEPER-103 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-103 Project: Zookeeper Issue Type: Improvement Components: build Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 3.0.0 Attachments: ZOOKEEPER-103.patch, ZOOKEEPER-103.sh This was sugested as way to bridge the gap in ZOOKEEPER-83 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-103) Reorganize the ZooKeeper source distro to follow maven conventions
[ https://issues.apache.org/jira/browse/ZOOKEEPER-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated ZOOKEEPER-103: Status: Patch Available (was: Open) Reorganize the ZooKeeper source distro to follow maven conventions -- Key: ZOOKEEPER-103 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-103 Project: Zookeeper Issue Type: Improvement Components: build Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 3.0.0 Attachments: ZOOKEEPER-103.patch, ZOOKEEPER-103.sh This was sugested as way to bridge the gap in ZOOKEEPER-83 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-103) Reorganize the ZooKeeper source distro to follow maven conventions
[ https://issues.apache.org/jira/browse/ZOOKEEPER-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620004#action_12620004 ] Hiram Chirino commented on ZOOKEEPER-103: - I think this patch is a nice middle ground. It's using only ANT, but adopting the maven directory conventions. So Pat's -1 does not really apply to this issue since ant is the only build system being used. Could the rest of the committers please post their thoughts on this? BTW once this is implemented, it should be easier to implement: ZOOKEEPER-95 and ZOOKEEPER-98 Reorganize the ZooKeeper source distro to follow maven conventions -- Key: ZOOKEEPER-103 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-103 Project: Zookeeper Issue Type: Improvement Components: build Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 3.0.0 Attachments: ZOOKEEPER-103.patch, ZOOKEEPER-103.sh This was sugested as way to bridge the gap in ZOOKEEPER-83 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-103) Reorganize the ZooKeeper source distro to follow maven conventions
[ https://issues.apache.org/jira/browse/ZOOKEEPER-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620013#action_12620013 ] Benjamin Reed commented on ZOOKEEPER-103: - I think we need to postpone this issue. It is causing a tremendous amount of distraction when we are right in the middle of getting out the next release. The proposal here conflicts with the proposal for maintaining recipes under contrib. It is also starting to hold up patches since the tree structure is considered in flux while this issue is open. In my opinion now is not the time for a tree restructuring. Lets focus on getting the patch backlog cleaned out and getting the release ready. Reorganize the ZooKeeper source distro to follow maven conventions -- Key: ZOOKEEPER-103 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-103 Project: Zookeeper Issue Type: Improvement Components: build Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 3.0.0 Attachments: ZOOKEEPER-103.patch, ZOOKEEPER-103.sh This was sugested as way to bridge the gap in ZOOKEEPER-83 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-110) Build script relies on svnant, which is not compatible with subversion 1.5 working copies
[
https://issues.apache.org/jira/browse/ZOOKEEPER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620037#action_12620037
]
Owen O'Malley commented on ZOOKEEPER-110:
-
My reading of the svnkit license would make it incompatible with the Apache
license. If it is incompatible, you can not depend on it or distribute it as
part of Zookeeper. See http://www.apache.org/legal/3party.html . If there isn't
away to avoid svnkit or fix svnant, you can ask legal about the TMate license.
In my opinion, the clause that will be fatal is:
{quote}
* Redistribution in any form without redistributing source code for software
that uses SVNKit is possible only when such redistribution is explictly
permitted
by TMate Software. Please, contact TMate Software at [EMAIL PROTECTED] to
get such permission.
{quote}
which is effectively a GPL-like viral clause with an escape clause that lets
TMate give/sell exceptions.
Build script relies on svnant, which is not compatible with subversion 1.5
working copies
-
Key: ZOOKEEPER-110
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-110
Project: Zookeeper
Issue Type: Bug
Components: build
Affects Versions: 3.0.0
Environment: Subversion 1.5 command line, or subclipse version 1.4.x
Reporter: Jakob Homan
Attachments: svntask.diff
The current build.xml ant script uses svnant to obtain the latest revision
number from the repo, however svnant is not compatible with subversion 1.5
(http://subversion.tigris.org/svn_1.5_releasenotes.html), and so the build
fails with working copies checked out by this version. The build fails with
this version of subversion is too old, please get a newer version... This
will become more apparent as svn 1.5 trickles out; I'm using a brand new dev
environment with both subclipse 1.4 and svn 1.5 client, so I got bit rather
quickly.
Those with svn 1.5 can get the code from the trunk, but cannot do an ant
build.
svnant hasn't been updated in more than a year and appears to be dead, so it
may no longer be a viable tool for the ant build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
