You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2009/11/23 08:02:39 UTC
[jira] Created: (ZOOKEEPER-590) review logging to ensure that
session related messages include session id
review logging to ensure that session related messages include session id
-------------------------------------------------------------------------
Key: ZOOKEEPER-590
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-590
Project: Zookeeper
Issue Type: Bug
Components: server
Reporter: Patrick Hunt
Fix For: 3.3.0
when the server is logging session related log messages it must include the session id in hex form
this greatly simplifies debugging - being able to relate a session message back to a particular session. otw there's
too much going on and there is no way to determine what messages are related to a particular session
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-590) review logging to ensure that
session related messages include session id
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt reassigned ZOOKEEPER-590:
--------------------------------------
Assignee: Patrick Hunt
> review logging to ensure that session related messages include session id
> -------------------------------------------------------------------------
>
> Key: ZOOKEEPER-590
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-590
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.3.0
>
>
> when the server is logging session related log messages it must include the session id in hex form
> this greatly simplifies debugging - being able to relate a session message back to a particular session. otw there's
> too much going on and there is no way to determine what messages are related to a particular session
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-590) review logging to ensure that
session related messages include session id
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-590:
-----------------------------------
Fix Version/s: (was: 3.3.0)
3.4.0
pushing to 3.4.0, not a blocker.
> review logging to ensure that session related messages include session id
> -------------------------------------------------------------------------
>
> Key: ZOOKEEPER-590
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-590
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.4.0
>
>
> when the server is logging session related log messages it must include the session id in hex form
> this greatly simplifies debugging - being able to relate a session message back to a particular session. otw there's
> too much going on and there is no way to determine what messages are related to a particular session
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.