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
}
		contentService.getActivationService().addExtensionActivationListener(activationListener);
	}
	/**
	 * Restores the working set filter from the persistence store.
	 */
	protected void initWorkingSetFilter(String workingSetName) {
		IWorkingSet workingSet = null;
		if (workingSetName != null && workingSetName.length() > 0) {
			IWorkingSetManager workingSetManager = PlatformUI.getWorkbench().getWorkingSetManager();
			workingSet = workingSetManager.getWorkingSet(workingSetName);
		} else if (PlatformUI.getPreferenceStore().getBoolean(
				IWorkbenchPreferenceConstants.USE_WINDOW_WORKING_SET_BY_DEFAULT)) {
			
			workingSet = PlatformUI.getWorkbench().getActiveWorkbenchWindow().getActivePage().getAggregateWorkingSet();
		}
		if (workingSet != null) {
			setWorkingSet(workingSet);
		}
	}
	/**
	 * Set current active working set.
	 * 
	 * @param workingSet
	 *            working set to be activated, may be <code>null</code>
	 */
	protected void setWorkingSet(IWorkingSet workingSet) {
		this.workingSet = workingSet;
		emptyWorkingSet = workingSet != null && workingSet.isAggregateWorkingSet() && workingSet.isEmpty();
		workingSetFilter.setWorkingSet(emptyWorkingSet ? null : workingSet);