so far as I know, you should keep an eye on your client handler and reconnect to Zookeeper server when it is expired youself. It's the solution in my application for this kind of situation.
On Wed, Apr 21, 2010 at 4:44 PM, Julien Vey <julien....@bull.net> wrote: > Hi all, > > I'm currently working with ZooKeeper in CXF D-OSGI and i'm facing a problem > that would require your help. > > When a client is connected to the ZooKeeper server, and the connection is > lost, it throws a ConnectionLossException. > The problem is when the connection is back, the client doesn't reconnect > itself. I can see the following trace on the server > > 2010-04-20 17:44:21,526 - INFO [NIOServerCxn.Factory:> > 0.0.0.0/0.0.0.0:2181:nioservercnxn$fact...@251] - Accepted socket > connection from /126.96.36.199:60471 > 2010-04-20 17:44:21,526 - INFO [NIOServerCxn.Factory: > 0.0.0.0/0.0.0.0:2181:nioserverc...@742] - Client attempting to renew > session0x1281ba54e900005 at /188.8.131.52:60471 > 2010-04-20 17:44:21,527 - INFO [NIOServerCxn.Factory: > 0.0.0.0/0.0.0.0:2181:nioserverc...@1424] - Invalid session > 0x1281ba54e900005 for client /184.108.40.206:60471, probably expired > 2010-04-20 17:44:21,527 - INFO [NIOServerCxn.Factory: > 0.0.0.0/0.0.0.0:2181:nioserverc...@1286] - Closed socket connection for > client /220.127.116.11:60471 which had sessionid 0x1281ba54e900005 > > The client tries to reconnect with an expired session id. > Is it possible to configure zookeeper in order that it accepts this > connection by recreating a new session, or maybe something else that would > make the reconnection works ? > > Thanks in advance for your help > > Julien. > > > > -- With Regards! Ye, Qian