Custom Logging is not working after Upgrade to WEM 8.1

After Upgrading to WEM 8.1, the custom logs are not writing to the log files.

In the existing code we used org.apache.log4j.Logger; for logging.

/apps/Vignette/vcm/inst-vgninst/logs/VgnVCM1-runtime.log is not updating with custom logging. This was working after upgrade to 8.0.1.

I can see there is lot of change in Logging in WEM 8.1.

Is there any configuration we have to do to work this?

Find more posts tagged with

Comments

Mario_Garcia

There were changes to the logging in 8.1 which affect custom logging. We now use a custom logger hierarchy by default. The vgnlog.xml file will only configure loggers in the custom hierarchy. In order to restore custom logging there are two options.

Create a custom log4j.properties file with your logger definitions and add it to the server classpath. This will configure the default logger hierarchy.
Add the JVM property -Dcom.vignette.logThirdparty=true to the server startup arguments. This restores 8.0 logging behavior.

I am sending you via email a PPT which contains the presentation I did for the 8.1 bootcamp.

Regards,

Mario

Quoted GangiReddy Nandyala (gangireddyn@virtusa.com) on 2011/05/25 07:58:

After Upgrading to WEM 8.1, the custom logs are not writing to the log files.

In the existing code we used org.apache.log4j.Logger; for logging.

/apps/Vignette/vcm/inst-vgninst/logs/VgnVCM1-runtime.log is not updating with custom logging. This was working after upgrade to 8.0.1.

I can see there is lot of change in Logging in WEM 8.1.

Is there any configuration we have to do to work this?

Annie_McCall

Hi Mario,

Can you please send me the ppt too? We also noticed after 8.1 upgrade our vcm-ui and vcm-api logs are longer being updated. Will doing your 2 suggestions above fix that?

Thanks,

Annie McCall

Mario_Garcia

Hi Annie,

In 8.1 the log entries for vcm-ui and vcm-api are all going to the VCM server runtime log instead of separate log files.

Regards,

Mario

Quoted Annie McCall (annmarie.mccall@prudential.com) on 2011/05/25 09:34:

Hi Mario,

Can you please send me the ppt too? We also noticed after 8.1 upgrade our vcm-ui and vcm-api logs are longer being updated. Will doing your 2 suggestions above fix that?

Thanks,

Annie McCall

Mario_Garcia

Since several people have requested the PowerPoint I will add the relevant information here. The PowerPoint includes additional implementation details that may not be of interest to most users.

The guideline for choosing one of the options for custom and thirdparty logging is the following:

Use the com.vignette.logThirdparty JVM property if you want to enable logging for thirdparty packages for debugging purposes (i.e. Axis or Spring). Log entries will appear in the VCM server runtime log.
Use a custom log4j.properties file if you have custom logging in your application and would like to log to a separate log file.

Enabling thirdparty logging using JVM property

Third party packages use the default hierarchy and do not log to the VCM runtime logs. To enable it, set the following JVM property in the command line arguments for the VCM server:

- Dcom.vignette.logThirdparty = true

This will force the logging system to revert back to using the default hierarchy for all loggers. So now both vignette and third party loggers will use the default hierarchy.

Configure loggers for your third party packages in the following file.

$INSTALLDIR/Content/8_1/adm/logging/vgnlog.xml

You may disable third-party logging after finished debugging.

Configure logging using a custom log4j.properties file

To configure logging using a custom log4j.propeties file you must place the log4j.properties file in the VCM server classpath.

Copy your custom log4j.properties file to a directory of your choice.
Add the directory to the VCM server classpath using the VCM Server WebLogic console.
Restart the VCM server

Since the vignette packages are using a custom hierarchy, they won't be affected by this log4j.properties file. They will continue to use the log settings specified in the vgnlog.xml file.

There are a few things that you need to be aware of if using this approach:

Since the server classpath already contains log4j.jar, your custom applications should not include log4j.jar in the APP-INF/lib or the WEB-INF/lib directories. Please remove log4j.jar from those locations.
Since logging is configured globally for the VCM server there should only be a single instance of log4j.properties in the server classpath.
Due to a build bug, a copy of log4j.properties is included in one of the jar files that ships with VCM (vgn-cap-service.jar)
The workaround for #3 is to remove log4j.properties from the following location.
- $INSTALLDIR/Content/8_1/rtsvcs/domains/vgndomain/servers/VgnVCMServer/stage/VgnContentSvcs/VgnContentSvcs.ear/APP-INF/lib/vgn-cap-service.jar!/log4j.properties