Performing a chunked updateNodeRightsContext() RightOperation.DELETE causes a thread crash/stack dum

I must be missing something obvious so I'm open to any suggestions. The environment is Content Server 10.5 patched to 2017-12 running on Windows/IIS, being called from a Java 1.8 application. I'm replacing permissions on a large number of objects using CWS from Java and when I pass an array containing copies of existing NodeRight to updateNodeRightsContext(), in order to remove the existing permissions, bad things happen resulting in a thread.out on the server with stack trace ("Status: An unknown feature was specified"). On the other hand if I copy the individual parts of each NodeRight to a new NodeRight object and add those to the array the call succeds perfectly. Here's the simplified code fragment: thisNodeRights = soapServices.docManClient().getNodeRights(thisNode.getID());; List thisNodeRightsOld = new ArrayList<>(); // copying the existing rights this way causes a thread crash // thisNodeRightsOld.add(thisNodeRights.getOwnerRight()); // but copying the existing rights this way works NodeRight oor = new NodeRight(); if (null != thisNodeRights.getOwnerRight()) { oor.setType(thisNodeRights.getOwnerRight().getType()); oor.setRightID(thisNodeRights.getOwnerRight().getRightID()); oor.setPermissions(thisNodeRights.getOwnerRight().getPermissions()); thisNodeRightsOld.add(oor); } ChunkedOperationContext thisNodeRightsDeleteContext = soapServices.docManClient().updateNodeRightsContext(thisNode.getID(), RightOperation.DELETE, thisNodeRightsOld, RightPropagation.TARGET_ONLY); soapServices.docManClient().updateNodeRights(thisNodeRightsDeleteContext);

Attached is an example of a trace.out produced when I add a NodeRight directly to the array, instead of reconstructing it. Looking at the trace I can see the expected bag of permissions copied in from the source object, and all those values all look valid and complete, so why is it unhappy?

Find more posts tagged with

Comments

AKropp

Hi Ameekul,

I’m not sure how helpful this will be since I’m not a Java guy, but I decided I’d mock it up in C# and see if I at least got some sort of similar result. The SDO for the NodeRights object returned by GetNodeRights seems a bit hairy and I’m not sure I understand what you’re doing to massage these values into a valid NodeRight array in the crashing case. In my own mockup I was pretty much forced to create a new array and copy the existing values into it because I didn’t see another way to do it – though I will admit I’m not exactly a code wizard here. I guess in your situation I would set up the code to create the NodeRight array using both methods, then inspect those objects in the debugger to see if you can spot the delta.

That said… CS should also handle this more gracefully. I’d suggest opening a support ticket so we can at least log a bug against that – I couldn’t see anything already existing. If nothing else we could stand to harden the function and return a proper exception.

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Tuesday, January 9, 2018 9:14 AM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: Performing a chunked updateNodeRightsContext() RightOperation.DELETE causes a thread crash/stack dump when the existing NodeRights to be actioned are copied instead of rebuilt? (JAVA)

Performing a chunked updateNodeRightsContext() RightOperation.DELETE causes a thread crash/stack dump when the existing NodeRights to be actioned are copied instead of rebuilt? (JAVA)

Posted byameekuls@opentext.com (Singh, Ameekul) On 01/09/2018 09:11 AM

I must be missing something obvious so I'm open to any suggestions. The environment is Content Server 10.5 patched to 2017-12 running on Windows/IIS, being called from a Java 1.8 application. I'm replacing permissions on a large number of objects using CWS from Java and when I pass an array containing copies of existing NodeRight to updateNodeRightsContext(), in order to remove the existing permissions, bad things happen resulting in a thread.out on the server with stack trace ("Status: An unknown feature was specified"). On the other hand if I copy the individual parts of each NodeRight to a new NodeRight object and add those to the array the call succeds perfectly. Here's the simplified code fragment: thisNodeRights = soapServices.docManClient().getNodeRights(thisNode.getID());; List thisNodeRightsOld = new ArrayList<>(); // copying the existing rights this way causes a thread crash // thisNodeRightsOld.add(thisNodeRights.getOwnerRight() ); // but copying the existing rights this way works NodeRight oor = new NodeRight(); if (null != thisNodeRights.getOwnerRight()) { oor.setType(thisNodeRights.getOwnerRight().getType()); oor.setRightID(thisNodeRights.getOwnerRight().getRightID()); oor.setPermissions(thisNodeRights.getOwnerRight().getPermissions()); thisNodeRightsOld.add(oor); } ChunkedOperationContext thisNodeRightsDeleteContext = soapServices.docManClient().updateNodeRightsContext(thisNode.getID(), RightOperation.DELETE, thisNodeRightsOld, RightPropagation.TARGET_ONLY); soapServices.docManClient().updateNodeRights(thisNodeRightsDeleteContext);

Attachment Links:

traceOut.txt (300 KB)

[To post a comment, use the normal reply function]
Forum:	Content Web Services Forum
Content Server:	My Support

Kris Boutilier

Hi, Alex. I'm Kris, the original poster for this issue, and an external customer. Ameekul works with the Website Support team and was assisting me with an issue with the forum wizard (my original posting was causing it to crash with 'Content Server Error: Could not invoke the method', apparently due to an improperly escaped character sequence).

Funny how a different day brings a different perspective... my mistake was basic - in the failing case the NodeRight for Owner was already null on most of my test nodes, so I was accidentially including null objects in the List sent to the ChunkedOperationContext, which triggers a thread crash. The safe approach is:

 if (null != thisNodeRights.getOwnerRight()) {     thisNodeRightsOld.add(thisNodeRights.getOwnerRight()); }

Unfortunately I don't have and dev experience with Content Server itself, nor tools to do any server-side debug, but I can certainly put this in to Support as a reproduceable condition that could be handled more gracefully.