You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/01/26 09:24:44 UTC
[jira] Created: (SMX4-748) Improve logging policy to avoid impact
on performances
Improve logging policy to avoid impact on performances
------------------------------------------------------
Key: SMX4-748
URL: https://issues.apache.org/jira/browse/SMX4-748
Project: ServiceMix 4
Issue Type: Bug
Reporter: Jean-Baptiste Onofré
Fix For: 4.3.0
Discussion with Claus on IRC:
<cibsen> any good reason why SMX logging is configured to use line logging?
<cibsen> thats slow
<cibsen> WARNING Generating caller location information is extremely slow and should be avoided unless execution speed is not an issue.
<cibsen> from the log4j manual
<cibsen> log4j.appender.out.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | %m%n
<cibsen> ah it was lower l which in fact is also slow
<cibsen> The location information can be very useful. However, its generation is extremely slow and should be avoided unless execution speed is not an issue.
<cibsen> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
<jbonofre> cibsen: no special reason
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SMX4-748) Improve logging policy to avoid impact
on performances
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMX4-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann reassigned SMX4-748:
-----------------------------------
Assignee: Lars Heinemann
> Improve logging policy to avoid impact on performances
> ------------------------------------------------------
>
> Key: SMX4-748
> URL: https://issues.apache.org/jira/browse/SMX4-748
> Project: ServiceMix 4
> Issue Type: Bug
> Reporter: Jean-Baptiste Onofré
> Assignee: Lars Heinemann
> Fix For: 4.3.0
>
>
> Discussion with Claus on IRC:
> <cibsen> any good reason why SMX logging is configured to use line logging?
> <cibsen> thats slow
> <cibsen> WARNING Generating caller location information is extremely slow and should be avoided unless execution speed is not an issue.
> <cibsen> from the log4j manual
> <cibsen> log4j.appender.out.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | %m%n
> <cibsen> ah it was lower l which in fact is also slow
> <cibsen> The location information can be very useful. However, its generation is extremely slow and should be avoided unless execution speed is not an issue.
> <cibsen> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
> <jbonofre> cibsen: no special reason
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMX4-748) Improve logging policy to avoid impact
on performances
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMX4-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann resolved SMX4-748.
---------------------------------
Resolution: Fixed
fixed
> Improve logging policy to avoid impact on performances
> ------------------------------------------------------
>
> Key: SMX4-748
> URL: https://issues.apache.org/jira/browse/SMX4-748
> Project: ServiceMix 4
> Issue Type: Bug
> Reporter: Jean-Baptiste Onofré
> Assignee: Lars Heinemann
> Fix For: 4.3.0
>
>
> Discussion with Claus on IRC:
> <cibsen> any good reason why SMX logging is configured to use line logging?
> <cibsen> thats slow
> <cibsen> WARNING Generating caller location information is extremely slow and should be avoided unless execution speed is not an issue.
> <cibsen> from the log4j manual
> <cibsen> log4j.appender.out.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | %m%n
> <cibsen> ah it was lower l which in fact is also slow
> <cibsen> The location information can be very useful. However, its generation is extremely slow and should be avoided unless execution speed is not an issue.
> <cibsen> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
> <jbonofre> cibsen: no special reason
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (SMX4-748) Improve logging policy to avoid
impact on performances
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMX4-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SMX4-748 started by Lars Heinemann.
> Improve logging policy to avoid impact on performances
> ------------------------------------------------------
>
> Key: SMX4-748
> URL: https://issues.apache.org/jira/browse/SMX4-748
> Project: ServiceMix 4
> Issue Type: Bug
> Reporter: Jean-Baptiste Onofré
> Assignee: Lars Heinemann
> Fix For: 4.3.0
>
>
> Discussion with Claus on IRC:
> <cibsen> any good reason why SMX logging is configured to use line logging?
> <cibsen> thats slow
> <cibsen> WARNING Generating caller location information is extremely slow and should be avoided unless execution speed is not an issue.
> <cibsen> from the log4j manual
> <cibsen> log4j.appender.out.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | %m%n
> <cibsen> ah it was lower l which in fact is also slow
> <cibsen> The location information can be very useful. However, its generation is extremely slow and should be avoided unless execution speed is not an issue.
> <cibsen> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
> <jbonofre> cibsen: no special reason
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.