Trying to lock files

Env. : TS 6.5 SP2 on Solaris

We have a small number of workflows that are 'stuck' because a task is trying to lock the attached DCR. I thought that by unlocking the file manually, the task would then lock the files and carry on, but nothing has happened in over 3 days. I know we have another issue causing this one but, does anyone know how often TeamSite attempts retry a task that cannot continue until it has the locks?

Thanks in advance.

Find more posts tagged with

Comments

kaalraa

Env. : TS 6.5 SP2 on Solaris
We have a small number of workflows that are 'stuck' because a task is trying to lock the attached DCR. I thought that by unlocking the file manually, the task would then lock the files and carry on, but nothing has happened in over 3 days. I know we have another issue causing this one but, does anyone know how often TeamSite attempts retry a task that cannot continue until it has the locks?
Thanks in advance.

On the first, please clarify as if you are using locktask or CLT iwlock?

If you are doing with the former, then it has to transition either to sucess or failure. What you can do.. if the locking fails, you can write an external script to unlock the files using iwunlock and then return back to your task. It would work as a loopback.

Mr_Cruise

It is a usertask and the lock attribute is set to true.

Sailesh

Is any of the files your workflow trying to aquire lock on already locked?

That could be one of the main reason for your workflow to behave in this way.

Let me know...

kaalraa

It is a usertask and the lock attribute is set to true.

From the manuals: -- When a locking task tries to acquire a lock for a file it checks first to see if that file is locked by some other task in its own job. If it is, the locking task “steals” the lock from the other ask. This behavior can result in submit time conflicts.

Mr_Cruise

Just to clear up some questions :-

For each stuck workflow the attached DCR was locked so I unlocked the DCR. I checked the manual and it states that TeamSite retrys every five minutes.

Adam Stoller

Just to clear up some questions :-

For each stuck workflow the attached DCR was locked so I unlocked the DCR. I checked the manual and it states that TeamSite retrys every five minutes.

Are you sure something else isn't taking over the lock before the workflow has a chance?

I've found that the lock="t" attribute tends to cause more problems than it solves and that you're generally better off using a locktask with a failure transition to an externaltask that runs iwunlock.ipl (IWOV supplies that script in IWHOME/local/bin) and then transition back to the locktask ... and on success transition to wherever you want.

Mr_Cruise

I have found out one new thing;

1. If I remove a workflow that is 'stuck' and re-submit the content through the same workflow it does not get stuck. Which is strange and kind of points to a TeamSite issue but the jury is still out on that one. We get on average 2 workflows hitting this issue and I cannot find a pattern yet.

I am tempted as suggested to insert a locktask before the usertask, as this may fix the problem or expose the real problem.

Any thoughts ?

Pawan

I have found out one new thing;

1. If I remove a workflow that is 'stuck' and re-submit the content through the same workflow it does not get stuck. Which is strange and kind of points to a TeamSite issue but the jury is still out on that one. We get on average 2 workflows hitting this issue and I cannot find a pattern yet.

This is strange! Well is it mostly the locking issue or something else ?

Sailesh

Always better to use locktask instead of lock='t'.

kaalraa

I have found out one new thing;
1. If I remove a workflow that is 'stuck' and re-submit the content through the same workflow it does not get stuck. Which is strange and kind of points to a TeamSite issue but the jury is still out on that one. We get on average 2 workflows hitting this issue and I cannot find a pattern yet.
I am tempted as suggested to insert a locktask before the usertask, as this may fix the problem or expose the real problem.
Any thoughts ?

Better log a case with IWOV Support.