Policy Server :: JVMoptions.txt : log4j

Document ID : KB000049602
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

I need to use a specific log4j version in the JVMoptions.txt file, and I noticed that if I put this version of log4j reference classpath after the smbootstrap.jar reference classpath, the JVM crashes because it tries to use the log4j 1.2.8 instead of the version that I need. How can I solve this?

Solution:

You will solve this problem by setting the JVMOptions.txt as the following:

-Xbootclasspath/p:C:/CA/siteminder/bin/endorsed/xercesImpl.jar;
C:/CA/siteminder/bin/endorsed/xml-apis.jar;
C:/CA/siteminder/bin/endorsed/resolver.jar;
C:/CA/siteminder/bin/endorsed/serializer.jar;
C:/CA/siteminder/bin/endorsed/commons-logging-1.1.1.jar;
C:/setup/files_from_customer/log4j-1.2.15.jar;
C:/setup/files_from_customer/commons-codec-1.3.jar;
C:/setup/files_from_customer/;
 
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
-Dlog4j.configuration=log4j.properties