Patrick Hunt commented on ZOOKEEPER-565:
Hm, I want to make sure I understand your issues. There is only one session
here - the zk client session. there's also a network connection (the socket)
this message is (should be) saying that the zk client lib attempted to
re-connect to the server but the client's ZK session has already expired on the
server (timeout exceeded, ephemerals cleaned up, etc...) and the ZK session is
no longer valid (ie the client needs to create a new session)
I'm happy to make this better (can't be much worse) but I want to make sure I
grok your request.
If this log message said something like
2009-10-29 14:25:54,023 - INFO ClientCnxn - Unable to reconnect to ZooKeeper
service, session 0x124a265d8b20001 has expired
would that be better? (notice info level since it's not really an error
your client watcher code is getting (in both cases) the watcher event that
notifies it of the session expiration, this is a log by the client library code
capturing the event.
> Revisit some java client log messages
> Key: ZOOKEEPER-565
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-565
> Project: Zookeeper
> Issue Type: Improvement
> Affects Versions: 3.2.1
> Reporter: Jean-Daniel Cryans
> As discussed during the 10/23 meeting, some messages in the java client logs
> are mixing up terms from different levels. For example:
> 2009-10-14 15:12:43,566 WARN org.apache.zookeeper.ClientCnxn: Exception
> closing session 0x1244f619478000d to sun.nio.ch.selectionkeyi...@15e32c4
> java.io.IOException: Session Expired
> at org.apache.zookeeper.ClientCnxn$SendThread.doIO(ClientCnxn.java:709)
> at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:945)
> Which session are we talking about in the first line? Now I know that it's a
> network-related session and not the ZK one, but I've seen many of our users
> getting confused over those lines.
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.