What is short lock and long lock in tibco iProcess?
- 1 Answers
- 9324 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
• Short lock. This is the standard lock normally set
by the TIBCO iProcess Workspace. A short lock is removed
when a user keeps or releases a work item. In the event
that short locks are left behind because, for example, the
iProcess Workspace crashed, the only way to remove the
short lock is to re-start the iProcess Engine or use the
following command.
• Long lock. A lock that is persistent and can only
be removed using sal_llock_frm_init() by the user holding
the lock. Long locks are not normally used by TIBCO
iProcess Workspace, but may be set by SAL SDK programs or
the TIBCO iProcess Objects Client. Re-starting the iProcess
Engine has no effect on long locks, so a work item locked
in this way remains inaccessible to every iProcess user
until it is manually unlocked.
| Is This Answer Correct ? | 17 Yes | 0 No |
Post New Answer View All Answers
how do you fire a boundary event pro-grammatically?
explain about routing?
What are the different types of event listener’s?
how do you access a child coach view?
what is the purpose of the dervied role?
What is WP12 MI without Synchronization?
what are teamworks components?
how a bpd can be divided into?
how do you assign the activities to users?
What is WP17 Interleaved Parallel Routing?
what is start message event listener?
what is event listener?
What is WP11 Implicit Termination?
what are different task types?
how do you enable javascript debugging for the coaches?
