Hi Satish,
This looks like a problem with your jvm 1.6 then. We use NIO framwork in
Java for receving and sending. We have seen NIO having some bugs on some
platforms. I am pretty sure that the problem you are seeing has something to
do with NIO in jvm 1.6 on mac.
Is it possible for you to use
Hi Satish,
This does sound a little weird since it works perfectly on my mac. Here
is my mac config--
9.4.0 Darwin Kernel Version 9.4.0: M
And java
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-11
Hi Satish,
This seems like a problem with svn 1.5 incompatibility with 1.4.
The jira
http://issues.apache.org/jira/browse/zookeeper-110
Fixes this issue but hasn¹t been checked in yet because its not compatible
with windows.
Can you try that patch and see if you can build it?
mahadev
On 8/7/
Hi satish,
Its not the same and has quite a few changes. The one on apache hasn¹t been
released yet. Can you download the trunk version and try it out? It will
help us going through the logs and match the lines. This is just for
debugging. For running in production I would still suggest using S
The only thing I see different is that you seem to be using an old version
of zookeeper on apache. Can you download trunk from
http://svn.apache.org/repos/asf/hadoop/zookeeper/trunk
And try it again?
The print statement --
³Trying to connect² is not there in the code any more. Can you try the
Hi Satish,
I just tried it on my mac and the client connects fine. I used your config
and
Echo ³stat² | nc localhost 2181 shows
Zookeeper version: 3.0.0-681910, built on 08/07/2008 17:32 GMT
Clients:
/0:0:0:0:0:0:0:1%0:65305[1](queued=0,recved=0,sent=0)
/0:0:0:0:0:0:0:1%0:65280[1](queued=0,re
For your example, do you see anything unusual in the server logs? Also did
you try --
Echo ³stat² | nc localhost 2181
Echo ³stat² | nc hostname 2181?
mahadev
On 8/7/08 10:11 AM, "Satish Bhatti" <[EMAIL PROTECTED]> wrote:
> Yeah, it works great on Ubuntu. Did you try it out on your Mac yet
Hi Satish,
I just ran the tests on my mac and saw that two of the tests quorumtest and
asynctest are failing. It looks like that there is a bind exception. Mac OS
does not seem to be cleaning up the ports fast enough for the tests to reuse
the ports. So the test failure mostly looks like bind prob
