ManagedObject.findByContentManagementId(id) in cma extension

If I call ManagedObject.findByContentManagementId(id) in cma extensions, it load the writable managedobject through EJB, and could cause dead lock issue, please refer to VOLLS ticktet 238697, what if I use ManagedObject.findByContentManagementId(id, RequestParameters. getImmutableInstanceTopRelationOnly() ), could that avoid loading writeable managedobject through EJB, then avoid dead lock?

Thank you

Alex

Find more posts tagged with

Comments

David_Stiles

I’m not sure why you’re encountering deadlocks withthis API, but the change you suggested doesn’t really do much differently.The only real difference, which perhaps could be significant depending on wherethe deadlocks are occurring, is that it you wont fetch sub-relation data, whichhas the effect of not including certain tables in the query performed. Thestate of the result objects being writeable or read-only is only determined byhow fully formed the result objects are. If you only request partially formedobjects, which is what RequestParameter.getImmutableInstanceTopRelationOnly()will do, then the objects will be marked read-only. Otherwise there is no realdifference in how the API is implemented.

From: eLink Entry:Vignette V7 and V8 Web Content Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, March 15, 2011 11:07 AM
To: eLink Recipient
Subject: ManagedObject.findByContentManagementId(id) in cma extension

ManagedObject.findByContentManagementId(id) in cma extension

Posted by alex.sun@bmo.com (Sun, Alex) On 2011/03/15 10:41

Thank you

Alex

[To post a comment, use the normal reply function]
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

Alex_Sun

David,

Thank you. On a workflow, the workflow first lock the content item, then update attribute value, then unlock it. Would this cause a deadlock? I tested this in unit test with jndi.properties connect to VCM, it looks fine as long as it is same user do lock and update, but I do have problem when this code in workflow. All the update information to toprelation(attribute value) has been lost, only relator information and content item approve status get updated.

Alex