Bug 5511

Summary: Review synchronization in MJFS.createManagedJob()
Product: GRAM Reporter: Martin Feller <feller@mcs.anl.gov>
Component: wsrf managed job factory serviceAssignee: Martin Feller <feller@mcs.anl.gov>
Status: CLOSED FIXED    
Severity: normal CC: feller@mcs.anl.gov, madduri@mcs.anl.gov, smartin@mcs.anl.gov
Priority: P3    
Version: unspecified   
Target Milestone: 4.0.6   
Hardware: Macintosh   
OS: All   

Description From 2007-08-30 11:37:02 
The creation of a job resource is synchronized. There had been
some very rare issues where a service thread creating a managed
job resource kept stuck and blocked subsequent threads an caused
all available service threads to be consumed. This finally caused
the container to keep stuck.
This synchronization seems to be unnecessary. However, if we
remove the synchronization here we must take care that access to
the idempotence id map managed in MEJHome is synchronized properly.
------- Comment #1 From 2007-11-30 22:54:58 ------- 
Access to the idempotence id map is properly synchronized.
I ran about 4-5 condor-g tests each with 1000 concurrent
jobs with removed synchronization without problems and
committed the change to the 4.0 branch.