Socket is not connected

2009-03-27 Thread Stefan Groschupf
Hi, I managed to upgrade my zookeeper 2 application to zookeeper 3.1.1/ All my tests run though my logs is full of following exception. In my code I basically just invoice ZooKeeper.close(); Any idea what the problem could be? Thanks, Stefan 09/03/27 02:07:51 INFO zookeeper.ZooKeeper:434 -

[jira] Updated: (ZOOKEEPER-356) Masking bookie failure during writes to a ledger

2009-03-27 Thread Flavio Paiva Junqueira (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-356: - Attachment: ZOOKEEPER-BOOKKEEPER-356.patch Masking bookie failure

Hudson build is back to normal: ZooKeeper-trunk #266

2009-03-27 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/266/changes

[jira] Commented: (ZOOKEEPER-353) javadoc warnings needs to be fixed

2009-03-27 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689897#action_12689897 ] Hudson commented on ZOOKEEPER-353: -- Integrated in ZooKeeper-trunk #266 (See

[jira] Commented: (ZOOKEEPER-354) to fix javadoc warning in the source files

2009-03-27 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689898#action_12689898 ] Hudson commented on ZOOKEEPER-354: -- Integrated in ZooKeeper-trunk #266 (See

[jira] Commented: (ZOOKEEPER-350) to run rats for releaseaudit

2009-03-27 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689899#action_12689899 ] Hudson commented on ZOOKEEPER-350: -- Integrated in ZooKeeper-trunk #266 (See

[jira] Commented: (ZOOKEEPER-351) to run checkstyle

2009-03-27 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689901#action_12689901 ] Hudson commented on ZOOKEEPER-351: -- Integrated in ZooKeeper-trunk #266 (See

[jira] Commented: (ZOOKEEPER-352) to add standard ant targets required by test-patch.sh script

2009-03-27 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689900#action_12689900 ] Hudson commented on ZOOKEEPER-352: -- Integrated in ZooKeeper-trunk #266 (See

Re: Socket is not connected

2009-03-27 Thread Patrick Hunt
Hi Stefan, There's a timing issue when the client closes the connection. It sends a session close to the server and then starts to close it's own sockets. If the server closes the socket before the client does you can sometimes see the client get java.net.SocketException: Socket is not

[jira] Resolved: (ZOOKEEPER-349) to automate patch testing

2009-03-27 Thread Mahadev konar (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar resolved ZOOKEEPER-349. - Resolution: Fixed Fix Version/s: 3.2.0 Hadoop Flags: [Reviewed] +1, i

[ANNOUNCE] Apache ZooKeeper 3.1.1

2009-03-27 Thread Patrick Hunt
The Apache ZooKeeper team is proud to announce Apache ZooKeeper version 3.1.1. ZooKeeper is a high-performance coordination service for distributed applications. It exposes common services - such as naming, configuration management, synchronization, and group services - in a simple interface

Re: Socket is not connected

2009-03-27 Thread Stefan Groschupf
Hi Patrick, thanks for the clarification. I can see your point but as user of zookeeper I personal would prefer to have this as debug message. Maybe something like log.debug(WARN: + msg). ... just a user feedback. Thanks, Stefan ~~~ Hadoop training and consulting

Re: Socket is not connected

2009-03-27 Thread Patrick Hunt
Thanks for the feedback. It's definitely not a clearcut decision on how to log it. As most ppl tend to run in INFO level on production systems we wanted to keep it visible for the time being. Patrick Stefan Groschupf wrote: Hi Patrick, thanks for the clarification. I can see your point but

[jira] Updated: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI

2009-03-27 Thread Giridharan Kesavan (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-60: Status: Patch Available (was: Open) Get cppunit tests running as part of

[jira] Updated: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI

2009-03-27 Thread Giridharan Kesavan (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-60: Status: Open (was: Patch Available) Get cppunit tests running as part of

[jira] Updated: (ZOOKEEPER-60) Get cppunit tests running as part of Hudson CI

2009-03-27 Thread Giridharan Kesavan (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated ZOOKEEPER-60: Status: Patch Available (was: Open) re-submitting the patch. Get cppunit