You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (Created) (JIRA)" <ji...@apache.org> on 2012/01/03 02:30:21 UTC

[jira] [Created] (KAFKA-231) avoid logging stacktrace directly

avoid logging stacktrace directly
---------------------------------

                 Key: KAFKA-231
                 URL: https://issues.apache.org/jira/browse/KAFKA-231
             Project: Kafka
          Issue Type: Improvement
          Components: core
            Reporter: Jun Rao
            Assignee: Jun Rao
             Fix For: 0.7.1
         Attachments: KAFKA-231.patch

There are several places where we log the stacktrace directly. This can be avoided by using the proper log4j method.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (KAFKA-231) avoid logging stacktrace directly

Posted by "Jun Rao (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KAFKA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jun Rao updated KAFKA-231:
--------------------------

    Status: Patch Available  (was: Open)

Patch attached.
                
> avoid logging stacktrace directly
> ---------------------------------
>
>                 Key: KAFKA-231
>                 URL: https://issues.apache.org/jira/browse/KAFKA-231
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>             Fix For: 0.7.1
>
>         Attachments: KAFKA-231.patch
>
>
> There are several places where we log the stacktrace directly. This can be avoided by using the proper log4j method.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (KAFKA-231) avoid logging stacktrace directly

Posted by "Jun Rao (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KAFKA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jun Rao updated KAFKA-231:
--------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Thanks for the review. Just committed this.
                
> avoid logging stacktrace directly
> ---------------------------------
>
>                 Key: KAFKA-231
>                 URL: https://issues.apache.org/jira/browse/KAFKA-231
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>             Fix For: 0.7.1
>
>         Attachments: KAFKA-231.patch
>
>
> There are several places where we log the stacktrace directly. This can be avoided by using the proper log4j method.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (KAFKA-231) avoid logging stacktrace directly

Posted by "Jun Rao (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KAFKA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jun Rao updated KAFKA-231:
--------------------------

    Attachment: KAFKA-231.patch
    
> avoid logging stacktrace directly
> ---------------------------------
>
>                 Key: KAFKA-231
>                 URL: https://issues.apache.org/jira/browse/KAFKA-231
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>             Fix For: 0.7.1
>
>         Attachments: KAFKA-231.patch
>
>
> There are several places where we log the stacktrace directly. This can be avoided by using the proper log4j method.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (KAFKA-231) avoid logging stacktrace directly

Posted by "Neha Narkhede (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KAFKA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178590#comment-13178590 ] 

Neha Narkhede commented on KAFKA-231:
-------------------------------------

+1
                
> avoid logging stacktrace directly
> ---------------------------------
>
>                 Key: KAFKA-231
>                 URL: https://issues.apache.org/jira/browse/KAFKA-231
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>             Fix For: 0.7.1
>
>         Attachments: KAFKA-231.patch
>
>
> There are several places where we log the stacktrace directly. This can be avoided by using the proper log4j method.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira