After upgrading to 6.8.0 and removing log4j-1.2.16.jar from actionslib, this jar is recreated in the actionslib folder on the agents.

Products

• CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

After upgrading the Nolio NAC and NES servers and agents to 6.8.0 and after removing the log4j-1.2.16.jar files from the actionslib folder, it appears these files are being recreated.
nimi.log shows: 
DEBUG (com.nolio.nimi.filetransfer.impl.FileTransferManagerImpl:409) - Making sure file with id `fid:####` gets written to `C:\####\CA\ReleaseAutomationAgent\actionslib\log4j-1.2.16.jar`

The log4j-1.2.16.jar is found in some Nexus repositories like:
ReleaseAutomationServer\sonatype-work\nexus\storage\nolio-actions\.nexus\attributes\default_actions_group\log4j\1.2.16
ReleaseAutomationServer\sonatype-work\nexus\storage\nolio-actions\default_actions_group\log4j\1.2.16

Environment

Nolio 6.8.0 upgraded from previous releases.

Resolution

To permanently prevent the log4j-1.2.16.jar files from being recreated:

1. Remove the row with FILE_NAME log4j-1.2.16.jar from the action_packs table.
2. Synchronise the DB: Either restart NAC or in JMX select: "noliocenter:type=info", the operation to invoke is syncWithRepository either with 'false' or 'true' flag

If the log4j-1.2.16.jar is found in some Nexus repositories like:
ReleaseAutomationServer\sonatype-work\nexus\storage\nolio-actions\.nexus\attributes\default_actions_group\log4j\1.2.16
ReleaseAutomationServer\sonatype-work\nexus\storage\nolio-actions\default_actions_group\log4j\1.2.16

Then after removing the log4j-1.2.16.jar from the action_packs table, the file can also be removed from the Nexus repositories using the Nexus repository manager. 
Login to the Nexus repository manager with the admin user. 
Then navigate to the log4j-1.2.16.jar file and remove.