Hi Aniruddha,

You don't need to run zookeeper separately. the test should run it. We've not tested Mac OS X Lion, but it does work on Snow Leopard.
I think this could be an IPv6 issue. I've not seen it on Mac before, but debian had a big issue with java when they enabled IPv6 by default.

The following lines illustrate the point.
<snip>
2012-03-02 12:00:18,263 - INFO  [Thread-2860-SendThread():ClientCnxn$SendThread@933][] - Opening socket connection to server /fe80:0:0:0:0:0:0:1%1:2181
2012-03-02 12:00:18,478 - INFO  [New I/O server worker #257-1-SendThread(localhost:33221):ClientCnxn$SendThread@933][] - Opening socket connection to server localhost/127.0.0.1:33221
2012-03-02 12:00:18,479 - WARN  [New I/O server worker #257-1-SendThread(localhost:33221):ClientCnxn$SendThread@1063][] - Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
</snip>

However, an ipv4 connection is successful further up. I think it's due to some connections using dns, and others not. it resolves "localhost" to  /fe80:0:0:0:0:0:0:1%1:2181, which doesn't work because zookeeper server doesn't listen on ipv6.

Could you try to apply the attached patch(cat NoLocalhostDNS.diff | patch -p0) and try again. If this works, could you open a JIRA (https://issues.apache.org/jira/browse/BOOKKEEPER) to resolve this issue permanently for lion users.

Attachment: NoLocalhostDNS.diff
Description: Binary data


-Ivan


On 2 Mar 2012, at 22:01, Aniruddha Laud wrote:

Hi Ivan, 

First of all, do I need to have a zookeeper instance running while building hedwig? 

$java -version 
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03-383-11A511c)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-383, mixed mode)

OS - Mac OS X Lion 10.7.3

It does seem that Zookeeper is failing. I've pasted the relevant info (From "Zookeeper server up and running" till I encounter the error) as an attachment. 

Regards, 
Aniruddha 







On Fri, Mar 2, 2012 at 1:46 AM, Ivan Kelly <[email protected]> wrote:
Hi Aniruddha,

It looks like zookeeper has died. Could you turn on logging and run again? To turn on logging, change the log4j.rootLogger line in hedwig-server/src/test/resources/log4j.properties from "OFF, CONSOLE" to "INFO, CONSOLE".

What kind of environment are you running this in? (OS, jvm version, etc)

-Ivan

On 1 Mar 2012, at 20:40, Aniruddha Laud wrote:

> Hi,
>
> I'm trying to build the latest release of hedwig and when I run "mvn
> package", I get build failures. I've pasted the error below. Any idea why
> this could be happening?
>
> Running org.apache.hedwig.server.TestPubSubServerStartup
> java.lang.Exception: Could not establish connection with ZooKeeper after
> zk_timeout*2 = 4000 ms. (Default value for zk_timeout is 2000).
>  at
> org.apache.hedwig.server.netty.PubSubServer.instantiateZookeeperClient(PubSubServer.java:165)
>
>  at
> org.apache.hedwig.server.netty.PubSubServer$3.run(PubSubServer.java:297)
>  at java.lang.Thread.run(Thread.java:680)
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.15 sec
> <<< FAILURE!
> Running org.apache.hedwig.server.topics.TestConcurrentTopicAcquisition
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.031 sec
> <<< FAILURE!
> Running org.apache.hedwig.server.topics.TestZkTopicManager
> Tests run: 10, Failures: 10, Errors: 0, Skipped: 0, Time elapsed: 0.147 sec
> <<< FAILURE!
> Running org.apache.hedwig.zookeeper.TestZkUtils
> Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.066 sec
> <<< FAILURE!
>
> Thanks.


<hedwig_fail.rtf>

Reply via email to