You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/04/09 13:31:13 UTC
[jira] Updated: (QPID-1799) Logging on critical path needs wrapping
to prevent expensive preparations
[ https://issues.apache.org/jira/browse/QPID-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1799:
---------------------------------
Description:
Summary:
If we have a log statement that does not take a single string as input then we should ensure that it is correctly wrapped with a isXEnabled call.
This should be true in general but on the critical delivery path then the performance overhead of building the string and not log it as the log level is not enabled is wasteful.
was:
Summary:
If we have a log statement that does not take a single string as input then we should ensure that it is correctly wrapped with a isXEnabled call.
> Logging on critical path needs wrapping to prevent expensive preparations
> -------------------------------------------------------------------------
>
> Key: QPID-1799
> URL: https://issues.apache.org/jira/browse/QPID-1799
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Critical
> Fix For: 0.5
>
>
> Summary:
> If we have a log statement that does not take a single string as input then we should ensure that it is correctly wrapped with a isXEnabled call.
> This should be true in general but on the critical delivery path then the performance overhead of building the string and not log it as the log level is not enabled is wasteful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org