Clarity PPM 12.0.1 - XOG errors - org.w3c.dom.DOMException: NAMESPACE_ERR:

[Anon Anon]

Hi All,

 

All of a sudden we are seeing following XOG errors in niku.log and the custom batch jobs are failing when xogging projects/cost plans -

niku.xog (WPTInterface:69839862__-398c2f27:XOG::project::write) Unhandled exception in prj_projects_write.xbl

org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.

 

Once we restart Clarity XOG services, these errors disappear.

These jobs used to run perfectly fine earlier. Since last week these errors have cropped up.

Note : we are clearing the Clarity cache continuously using a script.

 

Any pointers will be appreciated.

 

Thanks

Vidya

[navzjoshi00]

CLRT-14821 LOG[bg-niku]: Error: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.

 

Ignore the fact it says 'bg' and not 'app', that is just due to the original location it was found and reported, but I've seen this appear in both regardless. It's a strange defect, it strikes almost without warning, and can be quite persistent once it decides to surface in a part of the application, until you restart it and then it goes away (in most cases, seemingly 'forever', as it is rare to recur).

 

Fixes for it were introduced into Clarity 12.1.3 and 13.0.0 so that it wouldn't happen again, but until you're on those versions or higher, the only recourse is to restart the affected service and then try again.

 

The above was copied from the below thread (thanks to @Nick Darlington for the info on this ):

 

https://communities.ca.com/message/98971447#98971447

 

NJ

[Anon Anon]

Thanks for your response NJ. Since last week we are forced to restart Clarity XOG service almost every day as this error is

Leading to XOG failure in jobs. This is becoming a major concern.

Is there any more info on this bug fix?

 

Thanks,

Vidya

[navzjoshi00]

As has been mentioned in the thread,

"Fixes for it were introduced into Clarity 12.1.3 and 13.0.0 so that it wouldn't happen again, but until you're on those versions or higher, the only recourse is to restart the affected service and then try again."

 

NJ