nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Multiple workflow instances & single object

Imran_Yusubov

Hello Experts,

I am facing a problem in our environment.We have an ad-hoc workflow which have a dql write activity that updates same parameters of the package.

So far everything is ok. But the problem occurs if there are 2 or more instances of the process in the system with the same package.If two of the instances try to run the dql at the same time one of them fails ([DM_SYSOBJECT_E_VERSION_MISMATCH] error occurs).Because both process instances try to modify the same object at the same time. Is there any way to rescue from that problem? Please give me some suggestions.

Thanks in advance

error.txt

Find more posts tagged with

Comments

VadimYakovlev

Well, we do have a very similar problem.

I can't , at this point, think of anything else but the cusom activity method that would fetch the object and try to make an update to the object and catch the DM_SYSOBJECT_E_VERSION_MISMATCH and then try agin (with fetch) until it's succesful.

With some sort of failsafe in place, of cource.

Any other ideas, anyone?

DCTM_Guru

Strange. This type of error typically happens when you fetch an object (which creates a local cache) and then you try to update it after someone also fetches the object. DQL write should NOT fetch an object. Whats your UPDATE dql look like?

VadimYakovlev

Johnny, you're right, the UPDATE shold not fetch. Yet we don't know 100% what's goes on inside the "DQL Write activity". Maybe there's something like session.getObject (or fetch) befor the UPDATE takes place.

We have the same problem with the Process Data Mapping activity.

Imran_Yusubov

Hello,

you are right.This stuff had been working for s few months without any problems.But now I find out that in our development docbase it is failing.Can't understand what is the problem.

The dql is something like that,

"update dm_sysobject objects SET acl_name=? SET acl_domain=? where FOLDER(?,descend) and acl_name!=?"

When a case created I attach an acl to the case folder and it's descendants.

DCTM_Guru

If its only in DEV and that it was working before, then its probably something in your environment. Check your database. Maybe you are running out of TEMP space.

Imran_Yusubov

Hello Johnny,Vadim,

Thank you very much for your valuable response.I will check the database server and will let you know.

Thanks in advance

bacham2

Actually as of D6.0 DQL updates may perform a fetch. The reason is that DQL now handles TBOs. If you look behind the scenes, a DQL select is first performed, all objects are returned to the DFC client, TBO processing is performed on the DFC client and the changes are pushed back to the Content Server. All this happens in a transaction.

DCTM_Guru

Well if thats the case, then OP needs to lock the object before updating it and then unlock afterwards.