[cspadola]

We use the Object Lock Diagnostic Servlet in OTM and occasionally we get locked objects that stay locked until the app server is bounced. We routinely bounce our PROD environment on a weekly basis which will clear these locked objects (order releases). We know what is causing this (roughly 2-3 objects) and although we can wait until the weekly bounce while we resolve it permanently, I was wondering what possible harm there is if we use the "unlock" button beside each locked object within the servlet window?

Will using this button actually unlock the locked object and will the workflow pick up from where the object was locked? What possible issues could this cause?

Thanks.

[james_foran]

Hello,

I have seen similar issues in the Mediator. The were always on the CustomShipmentEvent. If this is the case, I know how to prevent it from occurring. First I will explain how the error occurs for CustomShipmentEvent:

1. An agent is triggered using a CustomShipmentEvent, which has been triggered from another agent. The triggering agent does NOT create a new Process.

2. The triggering agent, or an agent further downstream, also uses a CustomShipmentEvent, and also does NOT create a new process.

3. The Mediator is designed to prevent two similar tasks from executing on the same Business Object at the same time. In the above example, the only one CustomShipmentEvent can execute at the same time. The Second cannot start until the First has complete, and the first cannot complete until the Second has completed, as this is part of the same PROCESS.


Let me know if this helps.

Regards,

[james_foran]

Sorry, I forgot to add....

Using the UnLock feature will release the lock and allow the workflow to continue. How this works depends on how many locks for a single Business Object there are.