• Type: Bug
• Resolution: Fixed
• Priority: Medium
• Fix Version/s: 2.9.2
• Affects Version/s: 2.8
• Component/s: None
• Labels:

  • affects-server
  • logging&auditing
• Environment:

  Confluence Standalone on Sun JDK 5.0 Update 14,
  Apache Geronimo 2.1.2 with Tomcat container on IBM JDK 5.0 SR7 (Confluence WAR/EAR)

1. 

   Confluence-VelocityLog.jpg

   429 kB

   01/Jul/2008 5:16 PM

2. VelocityLog-on-ConfluenceStandalone.log

   11 kB

   07/Jul/2008 12:32 PM

[CONFSERVER-12291] Avalon Logkit library is missing.

Collapse comment: Andrew Lynch (Inactive) added a comment - 08/Sep/2008 3:19 AM

Andrew Lynch (Inactive) added a comment - 08/Sep/2008 3:19 AM

This issue has been resolved by fixing CONF-12816; Avalon Logkit has not been included as it is not necessary.

Expand comment: Andrew Lynch (Inactive) added a comment - 08/Sep/2008 3:19 AM

Andrew Lynch (Inactive) added a comment - 08/Sep/2008 3:19 AM This issue has been resolved by fixing CONF-12816 ; Avalon Logkit has not been included as it is not necessary.

Collapse comment: Matthew Leather added a comment - 20/Aug/2008 1:35 AM

Matthew Leather added a comment - 20/Aug/2008 1:35 AM

I think the separate bug of writing to velocity.log is caused by CONF-12816

Expand comment: Matthew Leather added a comment - 20/Aug/2008 1:35 AM

Matthew Leather added a comment - 20/Aug/2008 1:35 AM I think the separate bug of writing to velocity.log is caused by CONF-12816

Collapse comment: ConfluenceE added a comment - 01/Aug/2008 11:17 AM

ConfluenceE added a comment - 01/Aug/2008 11:17 AM

we just installed 2.8.2 and the same error appeared in our logs

cant`t we turn it of in any properties file ?

cheers
martin

Expand comment: ConfluenceE added a comment - 01/Aug/2008 11:17 AM

ConfluenceE added a comment - 01/Aug/2008 11:17 AM we just installed 2.8.2 and the same error appeared in our logs cant`t we turn it of in any properties file ? cheers martin

Collapse comment: Andrew Lynch (Inactive) added a comment - 08/Jul/2008 6:50 AM

Andrew Lynch (Inactive) added a comment - 08/Jul/2008 6:50 AM

Hi Kan,

My apologies, we are indeed missing that class from our distribution.

We specify

runtime.log.logsystem.class =com.atlassian.confluence.util.velocity.NullVelocityLogSystem

in our velocity.properties to suppress the writing of the Velocity log.

I noticed in your screenshot that it appears to be using the default velocity properties file which specifies

runtime.log.logsystem.class =org.apache.velocity.runtime.log.AvalonLogChute,org.apache.velocity.runtime.log.Log4JLogChute,org.apache.velocity.runtime.log.JdkLogChute

.

This appears to be a separate bug; we should never be writing to the velocity log. I was able to reproduce this locally using a standalone distribution.

Until we resolve this bug, I think you should be able to safely ignore it (it falls back to using a Log4jLogChute, and it should never be writing to the velocity log)

Expand comment: Andrew Lynch (Inactive) added a comment - 08/Jul/2008 6:50 AM

Andrew Lynch (Inactive) added a comment - 08/Jul/2008 6:50 AM Hi Kan, My apologies, we are indeed missing that class from our distribution. We specify runtime.log.logsystem.class =com.atlassian.confluence.util.velocity.NullVelocityLogSystem in our velocity.properties to suppress the writing of the Velocity log. I noticed in your screenshot that it appears to be using the default velocity properties file which specifies runtime.log.logsystem.class =org.apache.velocity.runtime.log.AvalonLogChute,org.apache.velocity.runtime.log.Log4JLogChute,org.apache.velocity.runtime.log.JdkLogChute . This appears to be a separate bug; we should never be writing to the velocity log. I was able to reproduce this locally using a standalone distribution. Until we resolve this bug, I think you should be able to safely ignore it (it falls back to using a Log4jLogChute, and it should never be writing to the velocity log)

Collapse comment: Kan Ogawa added a comment - 07/Jul/2008 12:32 PM

Kan Ogawa added a comment - 07/Jul/2008 12:32 PM

Andrew,

I attached the same log file that was printed on Confluence 2.8 standalone.
This issue is reproduced on this environment, too.

Also, the class "org.apache.log.format.Formatter" isn't contained in the "avalon-framework-4.2.0.jar" library.

Expand comment: Kan Ogawa added a comment - 07/Jul/2008 12:32 PM

Kan Ogawa added a comment - 07/Jul/2008 12:32 PM Andrew, I attached the same log file that was printed on Confluence 2.8 standalone. This issue is reproduced on this environment, too. Also, the class "org.apache.log.format.Formatter" isn't contained in the "avalon-framework-4.2.0.jar" library.

Collapse comment: Andrew Lynch (Inactive) added a comment - 07/Jul/2008 3:55 AM

Andrew Lynch (Inactive) added a comment - 07/Jul/2008 3:55 AM

Hi Kan,

We actually distribute version 4.2.0 of the Avalon Logkit library. Can you please check the contents of your WEB-INF/lib directory to ensure that it is there?

This is more likely than not a ClassLoading issue caused by your JDK and application server; I am guessing that Geronimo distributes its own version of this library?

Expand comment: Andrew Lynch (Inactive) added a comment - 07/Jul/2008 3:55 AM

Andrew Lynch (Inactive) added a comment - 07/Jul/2008 3:55 AM Hi Kan, We actually distribute version 4.2.0 of the Avalon Logkit library. Can you please check the contents of your WEB-INF/lib directory to ensure that it is there? This is more likely than not a ClassLoading issue caused by your JDK and application server; I am guessing that Geronimo distributes its own version of this library?