[
https://issues.apache.org/jira/browse/ZOOKEEPER-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655063#action_12655063
]
Patrick Hunt commented on ZOOKEEPER-222:
----------------------------------------
btw, iso8601 format we are using is: "yyyy-MM-dd HH:mm:ss,SSS"
(where SSS is milliseconds)
here's an example output in the new format:
2008-12-09 17:18:36,767:32455(0xb7e3bb90):[EMAIL PROTECTED]@1487: Got response
xid=fffffffe
> print C client log message timestamp in human readable form
> -----------------------------------------------------------
>
> Key: ZOOKEEPER-222
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-222
> Project: Zookeeper
> Issue Type: Improvement
> Components: c client
> Affects Versions: 3.0.0
> Reporter: Patrick Hunt
> Priority: Minor
> Fix For: 3.1.0
>
> Attachments: ZOOKEEPER-222.patch
>
>
> Noticed this issue during a debugging session -- it's difficult to
> read/compare the timestamps from the c client.
> The C client timestamp should be formatted with the same format as the JAVA
> log timestamps.
> Note: java uses ISO8601 timestamp formatting by default.
> Perhaps we should just bit the bullet and move to log4c? Consider this option
> when addressing this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.