Process failing with XOG error - Invalid request write for object customObjectInstance

[KriteeSaksena]

Hi,

 

 The process was failing with XOG error  - Invalid request write for object customObjectInstance, here is the sample XOG code within process

 

<NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_customObjectInstance.xsd">
<Header action="write" externalSource="NIKU" objectType="customObjectInstance" version="13.0.0.7032">
<args name="overrideAutoNumbering" value="false"/>
</Header>
<customObjectInstances objectCode="att_manual_forecast">
<instance instanceCode="5421024U4TDLL000EXP" objectCode="att_manual_forecast" parentInstanceCode="MP00007250" parentObjectCode="project">
<CustomInformation> <ColumnValue name="partition_code">NIKU.ROOT</ColumnValue>
<ColumnValue name="name">5421024U4TDLL000EXP</ColumnValue>
<ColumnValue name="code">5421024U4TDLL000EXP</ColumnValue>
<ColumnValue name="odf_parent_id">5421024</ColumnValue>
<ColumnValue name="odf_cncrt_parent_id">5421024</ColumnValue>
<ColumnValue name="att_forecas_currency">USD</ColumnValue>
<ColumnValue name="att_forecas">
<tsvData default="0.0" entityCode="AT&amp;T Fin Entity" finish="2018-12-31T00:00:00" fiscalPeriodType="MONTHLY" isFiscal="true" start="2018-03-01T00:00:00" type="value">
<segment finish="2018-03-31T00:00:00" isDefaultSegment="false" start="2018-03-01T00:00:00" value="410000"/>
<segment finish="2018-06-30T00:00:00" isDefaultSegment="false" start="2018-06-01T00:00:00" value="410000"/>
<segment finish="2018-09-30T00:00:00" isDefaultSegment="false" start="2018-09-01T00:00:00" value="410000"/>
<segment finish="2018-12-30T00:00:00" isDefaultSegment="false" start="2018-12-01T00:00:00" value="410000"/>
</tsvData>
</ColumnValue>
</CustomInformation>
</instance>
</customObjectInstances>
</NikuDataBus>

 

Output error -

 

<Status elapsedTime="0.0 seconds" state="FAILURE"/> <Statistics failureRecords="0" insertedRecords="0" totalNumberOfRecords="0" updatedRecords="0"/> <ErrorInformation> <Severity>FATAL</Severity> <Description>Exception while processing client request</Description> <Exception type="com.niku.xog.XOGException">Invalid request write for object customObjectInstance</Exception> </ErrorInformation>

 

This process started working fine after restarting app/bg, but anybody knows the reason of failure?

 

Thanks,

[Suman Pramanik]

Hi Kritee

 

When this happened prior to BG restart was any other process/jobs were working? If could be the information was held in cache and if something has interrupted the application could have ran into this issue

 

Regards

Suman Pramanik  

[KriteeSaksena]

Hi Suman,

 

it happend before bg restart. but other processes running at that time only this one was failing. But again we have 3 services so  I also checked the app and bg logs  and see this error there (see below) but no further details in both logs. and don't see any interruption captured in those logs during that time period when processes were failing with XOG error.

App Log details for failed instances.

ERROR 2018-02-19 01:06:04,337 [http-nio-7003-exec-194] util.ObjectRequestContext (clarity:admin:28432142__C2DE9907-FB28-4D07-BC20-0D02E54519CA:none) Invalid request write for object customObjectInstance
ERROR 2018-02-19 01:11:39,222 [http-nio-7003-exec-196] util.ObjectRequestContext (clarity:admin:28430558__5AF57B5F-A80C-4B4E-A452-70E25D7BDF0F:none) Invalid request write for object customObjectInstance
ERROR 2018-02-19 01:11:39,222 [http-nio-7003-exec-192] util.ObjectRequestContext (clarity:admin:28430557__9B92D555-B968-4288-9CE5-C1EA1B87BB91:none) Invalid request write for object customObjectInstance
ERROR 2018-02-19 01:15:26,455 [http-nio-7003-exec-197] util.ObjectRequestContext (clarity:admin:28430568__FA5D6833-51E6-499E-B36F-F66F6DC31E24:none) Invalid request write for object customObjectInstance
ERROR 2018-02-19 01:15:26,560 [http-nio-7003-exec-195] util.ObjectRequestContext (clarity:admin:28430567__F6864077-9B6D-44B1-B4F5-AEC1A9F02BD2:none) Invalid request write for object customObjectInstance
ERROR 2018-02-19 01:18:53,971 [http-nio-7003-exec-199] util.ObjectRequestContext (clarity:admin:28430573__A059A0B5-B6B5-42B8-BD0B-B19A74D9D024:none) Invalid request write for object customObjectInstance
ERROR 2018-02-19 01:18:55,038 [http-nio-7003-exec-199] util.ObjectRequestContext (clarity:admin:28430575__2631860B-F1EF-4B9D-A032-B31CD9B0506F:none) Invalid request write for object customObjectInstance
ERROR 2018-02-19 01:25:39,176 [http-nio-7003-exec-200] util.ObjectRequestContext (clarity:admin:28430583__21D0B6B2-3F57-484D-BE66-0EE8EA61E3D7:none) Invalid request write for object customObjectInstance
ERROR 2018-02-19 01:25:39,701 [http-nio-7003-exec-200] util.ObjectRequestContext (clarity:admin:28432151__3906D6AC-D2C6-4DFB-A648-1AEE284486C1:none) Invalid request write for object customObjectInstance

 

Please let me know if any other log you suggest me to check?

 

Thanks,

Kritee

[Legacy User]

Just to confirm, if you try XOGGing same using Offline Client works every single time?

[Legacy User]

Is this log failure for same instance or random instances? Is it like some works and some doesn't?

[KriteeSaksena]

Yes, XOG  working fine at present and process also working fine now, it was few process instances instances failed  at that time and we are trying to understand reason why it happened.  XOG user has all access rights and we don't see any service interruption at that time.

 

The log detail I sent, it has all failure for that process(XOG) at that time range.  but other processes were running fine.

also I tried to recreate the issue in lower instances  but not getting any error at all. so I am sure something was there at that time that was causing this particular XOG failure.

[Legacy User]

So it also look like you're xogging individual records. Kind of Many calls; sessions; login; logout. App may have some parameter setup howmany call it may do.

 

Just a random solution: Have tried making a batch like xx instances in one xog? If there are many being done not sure it's jamming the xog network. 

 

Because, as soon as you restart it starts working and fails again randomly. So code might be right just how App is processing them may be an issue.

 

In any case, records should be batched. XX nos. Should not do all in one as well as that could fail as well due to amount of memory app would require. For Ex. if you have 1000 to process process 100/250 batch.

[KriteeSaksena]

The process XOG one instance at a time. Process is on update process so we can not XOG in batched.

Any idea about "how App is processing them may be an issue."?

 

Because there were not many other processes/XOG were running at that time.