Clarity

Hi,

Can anyone help in regards to the below NAMESPACE_ERR.

I have managed to xogged in the below application instance to Dev environment but I can't into Production. Dev is the reflection of Production as refreshed from prod yesterday.


<XOGOutput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/status.xsd">
<Object type="application"/>
<Status state="FAILURE"/>
<Statistics failureRecords="1" insertedRecords="0"
totalNumberOfRecords="1" updatedRecords="0"/>
<Records>
<Record>
<KeyInformation>
<column name="ID">5033796</column>
<column name="name">Cheong Park Pavilion Redevelopment</column>
<column name="UNIQUE_NAME">EC0000000226</column>
</KeyInformation>[color=#910f29][color]
<ErrorInformation>
<Severity>FATAL</Severity>
<Description>XOG-3656: Investment Object operation failed: insert</Description>
<Exception><![CDATA[
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.

at org.apache.xerces.dom.ElementNSImpl.setName(Unknown Source)

at org.apache.xerces.dom.ElementNSImpl.<init>(Unknown Source)

at org.apache.xerces.dom.CoreDocumentImpl.createElementNS(Unknown Source)

at org.apache.xerces.dom.CoreDocumentImpl.importNode(Unknown Source)

at org.apache.xerces.dom.CoreDocumentImpl.importNode(Unknown Source)

You don't say which version of Clarity this is with, if it is 12.1.2 or lower, then I suspect it is this defect:

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.

Version 12.0.4.

Thanks Nick.

Restarted all services. It's working.

Hello,
can you please publish solution of this if you have any?
Regards,
Martin

Hi Shajik,

Are you using gelscript to xog the application or directly using console?

Dipanjan

Hello,
for me helped Flushing all caches. Check following topic:
2286155
Regards,
Martin

Thanks Martin.. :grin:

Dipanjan

Martin,

Though the issue is resolved, am curious about the root cause of the issue, what is the exact cause of the error, what is being stored in cache which is causing the issue. I checked in few other communities (java and ant), as per the discussions over there it appears to be something related to SOAP call.

As per the link that you have provided it is mentioned on upgrading java version it occurred in that case as well. But I am not sure if we can replicate the issue and if it is known bug.

Thanks,
Dipanjan