You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tubemq.apache.org by "Guocheng Zhang (Jira)" <ji...@apache.org> on 2020/06/17 11:42:00 UTC

[jira] [Commented] (TUBEMQ-243) Add some debug level logs to trace exceptions

    [ https://issues.apache.org/jira/browse/TUBEMQ-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138357#comment-17138357 ] 

Guocheng Zhang commented on TUBEMQ-243:
---------------------------------------

Yes, considering the needs of long-term operation, the logs in the project have been streamlined to avoid the log printing too much and cover the core information; if the detailed logs can be output after debugging mode is turned on, it will be a better solution.

> Add some debug level logs to trace exceptions
> ---------------------------------------------
>
>                 Key: TUBEMQ-243
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-243
>             Project: Apache TubeMQ
>          Issue Type: Improvement
>            Reporter: duli
>            Assignee: duli
>            Priority: Major
>
> Currently, the most codes in project only logged a brief exception message by log4j when throwing exception, and we can't get more exception stack trace for debugging, it is not convenient when happened an exception. So i want to add some debug level logs to trace the exception details.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)