Hi, I am trying to become familiar with the zookeeper API and am seeing
the following exceptions when attempting to create a node; any pointers
as to where to look for their cause would be greatly appreciated.
AFAIK, I am not doing anything special. I am running ZK standalone
using JDK 1.6 and
Forgot to mention, I am using the zookeeper-2.2.0.jar distribution.
Juan Ramirez wrote:
> Hi, I am trying to become familiar with the zookeeper API and am seeing
> the following exceptions when attempting to create a node; any pointers
> as to where to look for their cause would be greatly appre
I see this sometimes as well:
java.lang.RuntimeException: Unreasonable length = -183042030
at
com.yahoo.jute.BinaryInputArchive.readBuffer(BinaryInputArchive.java:101)
at
com.yahoo.zookeeper.proto.ConnectResponse.deserialize(ConnectResponse.java:59)
at
com.yahoo.zooke
Usually, this exception means that the server closed the socket. Are you
seeing anything strange in the server log?
The null pointer exception is coming from the code that parses the hostPort
list. Since you are running in standalone mode your hostPort should be a
string of the form host:port.
Hi, Ben. Thanks for the prompt reply.
Benjamin Reed wrote:
> Usually, this exception means that the server closed the socket. Are you
> seeing anything strange in the server log?
>
It seems like the server is expiring the session; not sure why.
2008-05-23 14:26:08,354 - WARN [NIOServerCxn.Fa
Hi Juan,
Can you tell us what you are doing in your client code and when you
see this problem? You are running with a standalone zookeeper server
right?
Mahadev
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:zookeeper-user-
> [EMAIL PROTECTED] On Behalf Of Juan Ramirez
> Sent: Fr
A bit more info in the trace file, but no obvious reason why the server
is expiring the session:
2008-05-23 14:25:47,267 - TRACE [main:[EMAIL PROTECTED] - Snapshotting: 0
2008-05-23 14:25:47,287 - TRACE [main:[EMAIL PROTECTED] - Snapshotting
finished: 0
2008-05-23 14:26:08,354 - WARN
[NIOServer
Mahadev Konar wrote:
> Hi Juan,
> Can you tell us what you are doing in your client code and when you
> see this problem?
Hi, Mahadev. It seems to happen when attempting to create a new node.
Might be a timing issue because it does not happen all the time. The
client code where this happens
A piece of info I left out which appears to be relevant is that I was
running the standalone server and its client on the same machine.
Perhaps this is not supported? I am not seeing the problem in a
clustered deployment with 5 zookeeper instances.
Thanks,
Juan
Juan Ramirez wrote:
> Mahadev
