Locked job not released

sgiang · Post by **sgiang** » Thu Mar 02, 2006 8:06 pm

Hi, guys

I have set the parameter start=1 in dsdlockd.config. All else remains as default. The daemon is running. It should wakeup every 15 minutes to cleanup defunct processes, right ? However, my job is still locked after 2.5 hrs. Does it mean that the the daemon is not working due to whatever reason ? Can someone explain this ?

Thanks.

Regards
Giang

ArndW · Post by **ArndW** » Fri Mar 03, 2006 2:11 am

You can check the daemon log file to see what it has been doing, but it should clear up locks for objects that it thinks are incorrect. If a lock is present because a process has aborted or had a "kill -9" done to it then the deadlock daemon will clean that up. If you have a lock held on a job by some active process then the deadlock daemon will take no action since it can't detect the difference between a valid user process and one that should no longer be running.

How did you locked job error come about? Could the locking process still be active?

kumar_s · Post by **kumar_s** » Fri Mar 03, 2006 2:23 am

If it is locked you should be able to see at cleanup resourse. And you can find the list of items holding the process by selecting the process id and Click on show by process.
If it as any valid job or record holded, you can close the job which holds the record or release it.

sgiang · Post by **sgiang** » Sun Mar 05, 2006 8:10 pm

Thanks, ArndW for the explanation.

I opened a job in Designer and the session was left idle, so it timed out, thus locking the job. So the configuration changes made to dsdlockd.config did not work in this case. Looks like I will need to unlock it in Director.

This leads me to another question, How can I set it such that my client session will not time-out ? I can't seem to be able to find it in Administrator.

Regards
Giang

ArndW wrote:You can check the daemon log file to see what it has been doing, but it should clear up locks for objects that it thinks are incorrect. If a lock is present because a process has aborted or had a "kill -9" done to it then the deadlock daemon will clean that up. If you have a lock held on a job by some active process then the deadlock daemon will take no action since it can't detect the difference between a valid user process and one that should no longer be running.

How did you locked job error come about? Could the locking process still be active?

chulett · Post by **chulett** » Sun Mar 05, 2006 8:25 pm

sgiang wrote:How can I set it such that my client session will not time-out ? I can't seem to be able to find it in Administrator.

It's there, right on the front from what I recall, but you need to be 'dsadm' to change it. Next to the timeout value is a checkbox to 'Never timeout'.

sgiang · Post by **sgiang** » Sun Mar 05, 2006 8:58 pm

Thanks, Craig. I got it now. I must be blind before.

Regards
Giang

chulett wrote:
sgiang wrote:How can I set it such that my client session will not time-out ? I can't seem to be able to find it in Administrator.

It's there, right on the front from what I recall, but you need to be 'dsadm' to change it. Next to the timeout value is a checkbox to 'Never timeout'.

ArndW · Post by **ArndW** » Mon Mar 06, 2006 12:49 am

sgiang wrote:...I opened a job in Designer and the session was left idle, so it timed out, thus locking the job. So the configuration changes made to dsdlockd.config did not work in this case...

That is exactly the kind of lock that the deadlock daemon will take care of.