ARP throws error code 400 after upgrade to 16.0.2 and does not display


Article ID: 242077


Updated On:


Clarity PPM SaaS


ITD ARP plugin uses log4j 1.x classes in their binaries as a dependency.  As we upgrade to clarity 16.0.2 we removed log4j 1.x jars and replaced with log4j 2.x jars. As a result when we load the ITD artifacts it can't find the required classes and throws an exception. ClarityContentFilter catches the exception thrown from underlying layers and converts to a bad request which is what customers observe in their browser as error 400.

Steps to Reproduce: 

  1. Open any clarity 16.0.2 environment with the ITD ARP plugin installed 
  2. Open the ARP (Home > Resource management > Advanced Resource Planning ) URL with action: https://cppmxxx/niku/  

Expected Results: ARP opens up for usage. 

Actual Results: ARP stuck with error 400 and cannot be loaded. 





Clarity 16.0.2

Component : Clarity add-ins / Plugins, Staffing, Assignments 


  • Targeted Fix in Release 16.0.3 
  • Targeted Fix in Release 16.0.2 Patch #1 ( 
  • GCP SaaS will have this fix implemented to all the customers in Release 16.0.2 Pre-Patch #1 

Additional Information