[ 
https://issues.apache.org/jira/browse/QPID-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-4124:
---------------------------------

    Affects Version/s: 0.17
                       0.14
                       0.15
                       0.16
        Fix Version/s:     (was: Future)
                       0.19
              Summary: [Java Broker] TransactionTimout logging has duplication 
and some erroneously uses default Object.toString  (was: TransactionTimout 
logging has duplication and some erroneously uses default Object.toString)
    
> [Java Broker] TransactionTimout logging has duplication and some erroneously 
> uses default Object.toString
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-4124
>                 URL: https://issues.apache.org/jira/browse/QPID-4124
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.14, 0.15, 0.16, 0.17, 0.18
>            Reporter: Philip Harvey
>            Assignee: Philip Harvey
>            Priority: Trivial
>             Fix For: 0.19
>
>         Attachments: 
> 0001-QPID-4124-Improved-logging-that-is-produced-when-the.patch, 
> 0001-QPID-4124-log-output-should-use-LogSubject.toLogStri.patch
>
>
> In AMQChannel, code such as 
> _logger.warn("IDLE TRANSACTION ALERT " + _logSubject.toString() ...
> should be replaced by 
> _logger.warn("IDLE TRANSACTION ALERT " + _logSubject.toLogString() ...
> because the first example uses Object.toString, which is not very useful for 
> logging.

--
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to