Applies: Quark Publishing Platform 15.x (QPP)
Solution: Below are the instructions to apply the hotfix in the Quark Publishing Platform:
- Stop Quark Publishing Platform Server and ensure that no instances of Quark Publishing Platform Server are running in the Task Manager.
-
Replace the old Log4j.jar files with the new Log4J-XXX-2.17.0.jar files:
- Navigate to the folder “[$Quark Publishing Platform Installation]\dependencies” (C:\Program Files\Quark\Quark Publishing Platform\dependencies).
- Take a backup of all the *.jar files whose name starts with “Log4J-XXX-2.*” from the folder C:\Program Files\Quark\Quark Publishing Platform\dependencies. For example, log4j-api-XXX.jar, log4j-core-XXX.jar
- Delete all the .jar files whose name starts with “Log4J-XXX-2.*” in the folder C:\Program Files\Quark\Quark Publishing Platform\dependencies. For example, log4j-api-2.8.2.jar, log4j-core-2.8.2.jar
- Copy the jar files extracted from Log4j_2.17_HotFix\QPP\Log4j_2.17_HotFix(QPP).zip” in the provided hotfix to the folder “C:\Program Files\Quark\Quark Publishing Platform\dependencies” as described in step a.
(for Quark Publishing Platform 15):
- log4j-core-2.17.0.jar
-
Modify the file “wrapper.conf” to adhere to the new version of log4j jar files.
- Take a backup of the file wrapper.conf from “[$Quark Publishing Platform Installation]\” (C:\Program Files\Quark\Quark Publishing Platform\ wrapper.conf)
- Edit the file wrapper.conf in “[$Quark Publishing Platform Installation]\” and then search and replace the following two instances of the log4j references (for QPP 15):
- Replace text - log4j-core-XXX.jar with log4j-core-2.17.0.jar
- Start Quark Publishing Platform Server and verify that the server is creating logs in the log files in “[$Quark Publishing Platform Installation]\log\.”
Priyanka Bhotika
Comments