[SMX4-748] Improve logging policy to avoid impact on performances

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.3.0
• Assignee: Lars Heinemann
• Reporter: Jean-Baptiste Onofré
• Created: 26/Jan/11 08:23
• Updated: 28/Jun/11 13:41
• Resolved: 28/Jan/11 13:35

Description

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

Issue Links

• relates to: SMX4-869 Missing class reference in the log:display output