XOG error message hitting XML Max Nodes - Clarity should provide exact amount of nodes
search cancel

XOG error message hitting XML Max Nodes - Clarity should provide exact amount of nodes

book

Article ID: 392934

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

The application should have a way of indicating the exact amount of XML Nodes there are in file, currently the output only shows current_limit which is not useful

STEPS TO REPRODUCE:

  1. Use a XOG file with high amount of nodes 
  2. Use legacy support recommendation for rough amount of nodes
  3. Note for the file provided Project_write.xml it seems to be 3.6M nodes
  4. Increase current_limit to 4000000 (4M) and attempt importing the file

or

  1. Or you can use any other file and system provided the file goes above the Max XML Node limit
  2. Import the file and check the XOG Output and app-ca log.

Expected Results; 

If the XOG import fails, it should also indicate either in app-ca log or XOG output or command line how many nodes the application has found in the file. It should state something like this (example):

Current XML Nodes in the file : ~4001000

If the application is able to determine the number of nodes, it should be able to provide this as a clear output 

Actual Results: 

XOG Import fails with error <Description>XOG-9060: The system cannot import this instance with the current configuration. Increase the governor limit of the 'Maximum XML Nodes' and try again.</Description>

No error in app-ca.log. If we enable DEBUG on com.niku.xog, we see just the below:

INFO  2025-03-23 00:55:48,831 [http-nio-80-exec-2] niku.xog (clarity:none:none:none) (ad4837d3-d369-45e2-8e01-10f377166661) Maximum XOG Governer Limit : 4000000

Environment

Clarity 16.3.1 and lower

Cause

DE168207

Resolution