You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Flavio Paiva Junqueira (JIRA)" <ji...@apache.org> on 2009/02/09 19:50:59 UTC
[jira] Created: (ZOOKEEPER-307) Log exception stack traces
Log exception stack traces
--------------------------
Key: ZOOKEEPER-307
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-307
Project: Zookeeper
Issue Type: Improvement
Affects Versions: 3.1.0
Reporter: Flavio Paiva Junqueira
Fix For: 3.2.0
For some exceptions, both on ZooKeeper and BookKeeper, we are calling printStackTrace explicitly instead of making a call to the logger.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-307) Log exception stack traces
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt resolved ZOOKEEPER-307.
------------------------------------
Resolution: Invalid
already addressed in separate jiras for 3.2
> Log exception stack traces
> --------------------------
>
> Key: ZOOKEEPER-307
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-307
> Project: Zookeeper
> Issue Type: Improvement
> Affects Versions: 3.1.0
> Reporter: Flavio Paiva Junqueira
> Fix For: 3.2.0
>
>
> For some exceptions, both on ZooKeeper and BookKeeper, we are calling printStackTrace explicitly instead of making a call to the logger.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.