[jira] Assigned: (ZOOKEEPER-564) Give more feedback on that current flow of events in java client logs

["Patrick Hunt (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt reassigned ZOOKEEPER-564:
--------------------------------------

    Assignee: Patrick Hunt

> Give more feedback on that current flow of events in java client logs
> ---------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-564
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-564
>             Project: Zookeeper
>          Issue Type: Improvement
>    Affects Versions: 3.2.1
>            Reporter: Jean-Daniel Cryans
>            Assignee: Patrick Hunt
>             Fix For: 3.3.0
>
>
> As discussed during the 10/23 meeting, one issue we have in debugging ZK client logs with HBase is that we have a hard time following the flow of events. It may be obvious for a ZK dev, but in our POV that kind of trace isn't very intuitive:
> {code}
> 2009-09-27 15:41:10,776 INFO org.apache.zookeeper.ClientCnxn: Attempting connection to server ...
> 2009-09-27 15:41:10,776 INFO org.apache.zookeeper.ClientCnxn: Priming connection to java.nio.channels.SocketChannel[connected local=/ ... remote=...
> 2009-09-27 15:41:10,776 INFO org.apache.zookeeper.ClientCnxn: Server connection successful 
> 2009-09-27 15:41:10,784 WARN org.apache.zookeeper.ClientCnxn: Exception closing session 0x0 to sun.nio.ch.SelectionKeyImpl@2c9b42e6
> {code}
> This excerpt is just an example. We would like to see something like a numbering of the events and possibly, in the case of an exception, at which point did it went wrong and what's the next step.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.