You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Dennis Lundberg (JIRA)" <ji...@apache.org> on 2009/12/29 17:34:30 UTC
[jira] Updated: (LOGGING-12) Jdk14Logger extremely slow due to
method name extraction
[ https://issues.apache.org/jira/browse/LOGGING-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated LOGGING-12:
-----------------------------------
Fix Version/s: 1.0.3
> Jdk14Logger extremely slow due to method name extraction
> --------------------------------------------------------
>
> Key: LOGGING-12
> URL: https://issues.apache.org/jira/browse/LOGGING-12
> Project: Commons Logging
> Issue Type: Bug
> Environment: Operating System: other
> Platform: Other
> Reporter: Bruno Dumon
> Fix For: 1.0.3
>
> Attachments: jdk14loggerpatch.txt
>
>
> The Jdk14Logger of Commons logging is *extremely* slow, even if logging is not
> enabled. This is due to the fact that an exception is created so that its stack
> trace can be used to determine the callers method name.
> Attached patch will surround the code with a logger.isLoggable(level) check, so
> that this is at least avoided when logging is not enabled. (though I would
> rather see that code completely removed)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.