Bug 262906 [http.registry]initializeDelegate in ServletManager.ServletWrapper should be synchronized
AB sent me an email which among things mentions a problem they encountered while load testing. "The servlet's init() methods are called multiple times whenever we make simultaneous requests to the server before they have been initialized." This is indeed a problem as we wrap each servlet that will look after lazily initializing the servlet and the relevant method -- initalizeMethod is not synchronized.
bundles/org.eclipse.ui.navigator.resources/src/org/eclipse/ui/internal/navigator/resources/actions/WorkingSetActionProvider.java
import org.eclipse.ui.navigator.CommonViewer;
import org.eclipse.ui.navigator.ICommonActionExtensionSite;
import org.eclipse.ui.navigator.IExtensionActivationListener;
import org.eclipse.ui.navigator.IExtensionStateModel;
import org.eclipse.ui.navigator.INavigatorContentService;
/**
 * @since 3.2
 * 
 */
public class WorkingSetActionProvider extends CommonActionProvider {
	private static final String TAG_CURRENT_WORKING_SET_NAME = "currentWorkingSetName"; 
	private boolean contributedToViewMenu = false;
	private CommonViewer viewer;
	private INavigatorContentService contentService;
	private WorkingSetFilterActionGroup workingSetActionGroup;
	private WorkingSetRootModeActionGroup workingSetRootModeActionGroup;
	private Object originalViewerInput = ResourcesPlugin.getWorkspace().getRoot();
	private IExtensionStateModel extensionStateModel;
	private final ResourceWorkingSetFilter workingSetFilter = new ResourceWorkingSetFilter();
	private boolean filterAdded;
	private boolean emptyWorkingSet;
	private IWorkingSet workingSet;
	private IPropertyChangeListener topLevelModeListener;
	
	private boolean ignoreFilterChangeEvents;
	/**
	 * Provides a smart listener to monitor changes to the Working Set Manager.
	 * 
	 */
	public class WorkingSetManagerListener implements IPropertyChangeListener {