[jira] Commented: (ZOOKEEPER-265) remove (deprecate) unused NoSyncConnected from KeeperState
[ https://issues.apache.org/jira/browse/ZOOKEEPER-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663309#action_12663309 ] Hudson commented on ZOOKEEPER-265: -- Integrated in ZooKeeper-trunk #194 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/194/]) . remove (deprecate) unused NoSyncConnected from KeeperState. (phunt via mahadev) remove (deprecate) unused NoSyncConnected from KeeperState -- Key: ZOOKEEPER-265 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-265 Project: Zookeeper Issue Type: Improvement Components: c client, java client, server Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-265.patch deprecate NoSyncConnected in KeeperState - it's not used anywhere in the codebase. what about Unknown? that seems to be unused as well, deprecate it as well? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-135) Fat jar build target
[ https://issues.apache.org/jira/browse/ZOOKEEPER-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663308#action_12663308 ] Hudson commented on ZOOKEEPER-135: -- Integrated in ZooKeeper-trunk #194 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/194/]) . Fat jar build target. (phunt and breed via mahadev) Fat jar build target Key: ZOOKEEPER-135 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-135 Project: Zookeeper Issue Type: New Feature Components: build Reporter: Benjamin Reed Assignee: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-135.patch, ZOOKEEPER-135.patch, ZOOKEEPER-135.patch, ZOOKEEPER-135.patch, ZOOKEEPER-135.patch For testing and experimentation purposes it would be nice to have everything in a self contained executable jar file that you can plop down on a machine and run. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-264) docs should include a state transition diagram for client state
[ https://issues.apache.org/jira/browse/ZOOKEEPER-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663336#action_12663336 ] Flavio Paiva Junqueira commented on ZOOKEEPER-264: -- Ben has already taken care of it. docs should include a state transition diagram for client state --- Key: ZOOKEEPER-264 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-264 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Assignee: Flavio Paiva Junqueira Priority: Minor Fix For: 3.1.0 we should have a state transition diagram to help users understand client state transitions. perhaps the edges could indicate what might cause such a transition? (not sure if that will work). keep in mind for the states that the java/c clients have diff names for constants (not sure how to handle). This should be added to the programmer guide in the appropriate section. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-264) docs should include a state transition diagram for client state
[ https://issues.apache.org/jira/browse/ZOOKEEPER-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira resolved ZOOKEEPER-264. -- Resolution: Fixed Assignee: Benjamin Reed (was: Flavio Paiva Junqueira) docs should include a state transition diagram for client state --- Key: ZOOKEEPER-264 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-264 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.0.0, 3.0.1 Reporter: Patrick Hunt Assignee: Benjamin Reed Priority: Minor Fix For: 3.1.0 we should have a state transition diagram to help users understand client state transitions. perhaps the edges could indicate what might cause such a transition? (not sure if that will work). keep in mind for the states that the java/c clients have diff names for constants (not sure how to handle). This should be added to the programmer guide in the appropriate section. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-272) getChildren can fail for large numbers of children
getChildren can fail for large numbers of children -- Key: ZOOKEEPER-272 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-272 Project: Zookeeper Issue Type: Bug Reporter: Joshua Tuberville Zookeeper allows creation of an abritrary number of children, yet if the String array of children names exceeds 4,194,304 bytes a getChildren will fail because ClientCnxn$SendThread.readLength() throws an exception on line 490. Mahadev Konar questioned this byte limit's need. In any case consistency of create children, get children should exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-272) getChildren can fail for large numbers of children
[ https://issues.apache.org/jira/browse/ZOOKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663418#action_12663418 ] Benjamin Reed commented on ZOOKEEPER-272: - I think there are two stages to fixing this problem. First we should make that line of code use BinaryInputArchive.maxBuffer, so that it can be configured. Then we should probably add a version of getChildren that takes and returns an offset, so that getChildren could be called multiple times to get all of the children. getChildren can fail for large numbers of children -- Key: ZOOKEEPER-272 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-272 Project: Zookeeper Issue Type: Bug Reporter: Joshua Tuberville Zookeeper allows creation of an abritrary number of children, yet if the String array of children names exceeds 4,194,304 bytes a getChildren will fail because ClientCnxn$SendThread.readLength() throws an exception on line 490. Mahadev Konar questioned this byte limit's need. In any case consistency of create children, get children should exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-272) getChildren can fail for large numbers of children
[ https://issues.apache.org/jira/browse/ZOOKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663422#action_12663422 ] Mahadev konar commented on ZOOKEEPER-272: - returning an offset for getchildren is a good suggestion should we just fix the limit in this jira and open another one for getchildren returning an offset ? fixing the limit would be easir to do and can be a part of 3.1 release. getChildren can fail for large numbers of children -- Key: ZOOKEEPER-272 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-272 Project: Zookeeper Issue Type: Bug Reporter: Joshua Tuberville Zookeeper allows creation of an abritrary number of children, yet if the String array of children names exceeds 4,194,304 bytes a getChildren will fail because ClientCnxn$SendThread.readLength() throws an exception on line 490. Mahadev Konar questioned this byte limit's need. In any case consistency of create children, get children should exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-234) Eliminate using statics to initialize the sever. Should allow server to be more embeddable in OSGi enviorments.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt reassigned ZOOKEEPER-234:
--
Assignee: Patrick Hunt
Eliminate using statics to initialize the sever. Should allow server to be
more embeddable in OSGi enviorments.
Key: ZOOKEEPER-234
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-234
Project: Zookeeper
Issue Type: Improvement
Components: server
Reporter: Hiram Chirino
Assignee: Patrick Hunt
Fix For: 3.1.0
Attachments: ZOOKEEPER-234_step1.patch, ZOOKEEPER-234_step3.patch
Patrick request I open up this in issue in this [email
thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html]
The main culprit I've noticed is:
{code}
ServerStats.registerAsConcrete();
{code}
But there may be others.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-234) Eliminate using statics to initialize the sever. Should allow server to be more embeddable in OSGi enviorments.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-234:
---
Attachment: ZOOKEEPER-234_step3.patch
step 3 of the patch(see comment to follow on how to apply)
Eliminate using statics to initialize the sever. Should allow server to be
more embeddable in OSGi enviorments.
Key: ZOOKEEPER-234
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-234
Project: Zookeeper
Issue Type: Improvement
Components: server
Reporter: Hiram Chirino
Assignee: Patrick Hunt
Fix For: 3.1.0
Attachments: ZOOKEEPER-234_step1.patch, ZOOKEEPER-234_step3.patch
Patrick request I open up this in issue in this [email
thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html]
The main culprit I've noticed is:
{code}
ServerStats.registerAsConcrete();
{code}
But there may be others.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-234) Eliminate using statics to initialize the sever. Should allow server to be more embeddable in OSGi enviorments.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-234:
---
Attachment: ZOOKEEPER-234_step1.patch
step1 of the patch (see comment to follow on how to apply)
Eliminate using statics to initialize the sever. Should allow server to be
more embeddable in OSGi enviorments.
Key: ZOOKEEPER-234
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-234
Project: Zookeeper
Issue Type: Improvement
Components: server
Reporter: Hiram Chirino
Fix For: 3.1.0
Attachments: ZOOKEEPER-234_step1.patch, ZOOKEEPER-234_step3.patch
Patrick request I open up this in issue in this [email
thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html]
The main culprit I've noticed is:
{code}
ServerStats.registerAsConcrete();
{code}
But there may be others.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-234) Eliminate using statics to initialize the sever. Should allow server to be more embeddable in OSGi enviorments.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663566#action_12663566
]
Patrick Hunt commented on ZOOKEEPER-234:
The two attached patches should be applied as follows:
apply the first patch step 1
then:
mkdir src/java/main/org/apache/zookeeper/jmx
svn add src/java/main/org/apache/zookeeper/jmx
svn mv src/java/jmx/org/apache/zookeeper/server/ManagedUtil.java
src/java/main/org/apache/zookeeper/jmx/.
svn mv src/java/jmx/org/apache/zookeeper/jmx/*.java
src/java/main/org/apache/zookeeper/jmx
svn mv src/java/jmx/org/apache/zookeeper/jmx/server/*.java
src/java/main/org/apache/zookeeper/server/.
svn mv src/java/jmx/org/apache/zookeeper/jmx/server/quorum/*.java
src/java/main/org/apache/zookeeper/server/quorum/.
svn rm --force src/java/jmx
then:
apply second patch step 3
after this process the src/java/jmx directory should be no longer
run ant test to verify. also start a zkserver as follows and verify that
jconsole can connect:
java -cp zookeeper-dev.jar:src/java/lib/log4j-1.2.15.jar:conf
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=false
org.apache.zookeeper.server.quorum.QuorumPeerMain zoo.cfg
then: commit to svn if tests/smoketest all pass
Eliminate using statics to initialize the sever. Should allow server to be
more embeddable in OSGi enviorments.
Key: ZOOKEEPER-234
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-234
Project: Zookeeper
Issue Type: Improvement
Components: server
Reporter: Hiram Chirino
Assignee: Patrick Hunt
Fix For: 3.1.0
Attachments: ZOOKEEPER-234_step1.patch, ZOOKEEPER-234_step3.patch
Patrick request I open up this in issue in this [email
thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html]
The main culprit I've noticed is:
{code}
ServerStats.registerAsConcrete();
{code}
But there may be others.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (ZOOKEEPER-234) Eliminate using statics to initialize the sever. Should allow server to be more embeddable in OSGi enviorments.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663566#action_12663566
]
phunt edited comment on ZOOKEEPER-234 at 1/13/09 4:17 PM:
-
The attached patches will:
* remove the static stat classes
* remove the src/java/jmx subdir and integrate into the mainline
* as a result all zookeeper servers will now have jmx support by default
* adds jmx support for log4j as well
* fixes a number of issues with the structure and data in jmx for zk server(s)
The two attached patches should be applied as follows:
apply the first patch step 1
then:
mkdir src/java/main/org/apache/zookeeper/jmx
svn add src/java/main/org/apache/zookeeper/jmx
svn mv src/java/jmx/org/apache/zookeeper/server/ManagedUtil.java
src/java/main/org/apache/zookeeper/jmx/.
svn mv src/java/jmx/org/apache/zookeeper/jmx/*.java
src/java/main/org/apache/zookeeper/jmx
svn mv src/java/jmx/org/apache/zookeeper/jmx/server/*.java
src/java/main/org/apache/zookeeper/server/.
svn mv src/java/jmx/org/apache/zookeeper/jmx/server/quorum/*.java
src/java/main/org/apache/zookeeper/server/quorum/.
svn rm --force src/java/jmx
then:
apply second patch step 3
after this process the src/java/jmx directory should be no longer
run ant test to verify. also start a zkserver as follows and verify that
jconsole can connect:
java -cp zookeeper-dev.jar:src/java/lib/log4j-1.2.15.jar:conf
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=false
org.apache.zookeeper.server.quorum.QuorumPeerMain zoo.cfg
then: commit to svn if tests/smoketest all pass
was (Author: phunt):
The two attached patches should be applied as follows:
apply the first patch step 1
then:
mkdir src/java/main/org/apache/zookeeper/jmx
svn add src/java/main/org/apache/zookeeper/jmx
svn mv src/java/jmx/org/apache/zookeeper/server/ManagedUtil.java
src/java/main/org/apache/zookeeper/jmx/.
svn mv src/java/jmx/org/apache/zookeeper/jmx/*.java
src/java/main/org/apache/zookeeper/jmx
svn mv src/java/jmx/org/apache/zookeeper/jmx/server/*.java
src/java/main/org/apache/zookeeper/server/.
svn mv src/java/jmx/org/apache/zookeeper/jmx/server/quorum/*.java
src/java/main/org/apache/zookeeper/server/quorum/.
svn rm --force src/java/jmx
then:
apply second patch step 3
after this process the src/java/jmx directory should be no longer
run ant test to verify. also start a zkserver as follows and verify that
jconsole can connect:
java -cp zookeeper-dev.jar:src/java/lib/log4j-1.2.15.jar:conf
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=false
org.apache.zookeeper.server.quorum.QuorumPeerMain zoo.cfg
then: commit to svn if tests/smoketest all pass
Eliminate using statics to initialize the sever. Should allow server to be
more embeddable in OSGi enviorments.
Key: ZOOKEEPER-234
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-234
Project: Zookeeper
Issue Type: Improvement
Components: server
Reporter: Hiram Chirino
Assignee: Patrick Hunt
Fix For: 3.1.0
Attachments: ZOOKEEPER-234_step1.patch, ZOOKEEPER-234_step3.patch
Patrick request I open up this in issue in this [email
thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html]
The main culprit I've noticed is:
{code}
ServerStats.registerAsConcrete();
{code}
But there may be others.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-34) Optimize string deserialization
[ https://issues.apache.org/jira/browse/ZOOKEEPER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-34: -- Fix Version/s: (was: 3.1.0) 3.2.0 Optimize string deserialization --- Key: ZOOKEEPER-34 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-34 Project: Zookeeper Issue Type: New Feature Components: server Reporter: Patrick Hunt Fix For: 3.2.0 Moved from SourceForge to Apache. http://sourceforge.net/tracker/index.php?func=detailaid=1952497group_id=209147atid=1008547 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-146) Allow clients to retrieve the list of hosts/servers from a URL
[ https://issues.apache.org/jira/browse/ZOOKEEPER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-146: --- Fix Version/s: (was: 3.1.0) 3.2.0 Allow clients to retrieve the list of hosts/servers from a URL -- Key: ZOOKEEPER-146 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-146 Project: Zookeeper Issue Type: Improvement Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.2.0 Attachments: ZOOKEEPER-146.patch As I suggested in ZOOKEEPER-107, it would be nice to allow clients to specify their hosts strings via a URL so that this can change dynamically. For instance, obtain the current list of hosts from a webpage or a file on disk. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-148) add jdiff support to zookeeper release process
[ https://issues.apache.org/jira/browse/ZOOKEEPER-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-148: --- Fix Version/s: (was: 3.1.0) 3.2.0 add jdiff support to zookeeper release process -- Key: ZOOKEEPER-148 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-148 Project: Zookeeper Issue Type: Improvement Components: build Reporter: Patrick Hunt Priority: Minor Fix For: 3.2.0 Add jdiff support to enable detailed release notes on changes to java. Hadoop just added code for including that in the build: HADOOP-2421. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-149) c interface is missing tests against java server (mock only)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-149: -- Assignee: Benjamin Reed (was: Patrick Hunt) Ben is looking at system test as part of ZOOKEEPER-215 c interface is missing tests against java server (mock only) Key: ZOOKEEPER-149 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-149 Project: Zookeeper Issue Type: Improvement Components: c client Reporter: Patrick Hunt Assignee: Benjamin Reed Fix For: 3.1.0 The c client interface has unit tests but they are against mock server implementations only. We need to add tests for the c interface against live java server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-177) needed: docs for JMX
[ https://issues.apache.org/jira/browse/ZOOKEEPER-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-177: -- Assignee: Patrick Hunt needed: docs for JMX Key: ZOOKEEPER-177 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-177 Project: Zookeeper Issue Type: Improvement Components: documentation, jmx Reporter: Robbie Scott Assignee: Patrick Hunt Fix For: 3.1.0 I don't know if this should be part of the logging section in the zookeeper admin guide (see JIRA ZOOKEEPER-166 ) but, per Patrick, related to security, ack, yea another doc, is the documentation of the JMX support that zk has -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-195) Configuration information is spread across too many docs. Consolidate into one
[ https://issues.apache.org/jira/browse/ZOOKEEPER-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-195: --- Fix Version/s: (was: 3.1.0) 3.2.0 Configuration information is spread across too many docs. Consolidate into one -- Key: ZOOKEEPER-195 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-195 Project: Zookeeper Issue Type: Improvement Components: documentation Affects Versions: 3.0.0 Reporter: Robbie Scott Priority: Minor Fix For: 3.2.0 Attachments: ZOOKEEPER-195.patch Original Estimate: 1h Remaining Estimate: 1h There are definition lists of the configuration parameters in both the getting started guide and in the admin guide. It should probably only exist in the administration guide in the configuration parameters section. Note that in the getting started guide, definitions of config params can be found in both - Installing and Running ZooKeeper in Single Server Mode - Running Replicated ZooKeeper -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-216) Improve logging in C client
[ https://issues.apache.org/jira/browse/ZOOKEEPER-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-216: --- Fix Version/s: (was: 3.1.0) 3.2.0 Improve logging in C client --- Key: ZOOKEEPER-216 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-216 Project: Zookeeper Issue Type: Improvement Components: c client Affects Versions: 3.0.0 Reporter: Patrick Hunt Fix For: 3.2.0 While debugging a client issue we saw multiple areas for improvement in C logging. It might be a good idea to also move to log4c. Anyone have experience with this? multithread an issue? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-240) Yet another npe
[ https://issues.apache.org/jira/browse/ZOOKEEPER-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-240. Resolution: Fixed Assignee: Patrick Hunt fixed as part of ZOOKEEPER-268 Yet another npe --- Key: ZOOKEEPER-240 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-240 Project: Zookeeper Issue Type: Bug Components: java client Affects Versions: 3.0.1 Reporter: Flavio Paiva Junqueira Assignee: Patrick Hunt Fix For: 3.1.0 java.lang.NullPointerException at org.apache.jute.Utils.toCSVBuffer(Utils.java:234) at org.apache.jute.CsvOutputArchive.writeBuffer(CsvOutputArchive.java:101) at org.apache.zookeeper.proto.GetDataResponse.toString(GetDataResponse.java:48) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.apache.zookeeper.ClientCnxn$Packet.toString(ClientCnxn.java:230) at java.lang.String.valueOf(String.java:2827) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:586) at org.apache.zookeeper.ClientCnxn$SendThread.doIO(ClientCnxn.java:626) at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:852) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-254) there is currently no way for a user to test session expiration in their code
[ https://issues.apache.org/jira/browse/ZOOKEEPER-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-254: -- Assignee: Benjamin Reed Ben said he had an idea - to document in faq. there is currently no way for a user to test session expiration in their code - Key: ZOOKEEPER-254 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-254 Project: Zookeeper Issue Type: Bug Components: tests Reporter: Patrick Hunt Assignee: Benjamin Reed Fix For: 3.1.0 There's currently no way for a user to test session expiration in their code. We don't have any unit/system tests that verify our code handles session expiration properly. There should be a way to test session expiration. I did notice that we have the ability to terminate a session using JMX mbean interface, however I'm not sure if this is useful in an automated testing context. Even if it is we should provide a wrapper for testing purposes - and add tests to our codebase which uses it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-231) Quotas in zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-231: Attachment: ZOOKEEPER-231.patch here is a more recent patch (needs testing). it does not include tests and docs -- will be adding them. Quotas in zookeeper --- Key: ZOOKEEPER-231 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-231 Project: Zookeeper Issue Type: New Feature Affects Versions: 3.0.0 Reporter: Mahadev konar Assignee: Mahadev konar Fix For: 3.1.0 Attachments: ZOOKEEPER-231.patch, ZOOKEEPER-231.patch creating quota's in zookeeper so that a runaway application does not bring down the zookeeper cluster. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
