When running on MSSQL 2005 we are experiencing blocking issues in JBPM_JOB table which essentially stalls processing of jobs for extended period of time. Looks like exclusive lock is held on the job table. Tried turning off lock escalation, but that had no affect. The only thing that seems to work is setting transaction isolation level to TRANSACTION_READ_UNCOMMITTED. Is it safe to to set transaction isolation level to READ_UNCOMMITTED? Is there another, safer solution to this problem? Thank you in advance for any insight you can offer!