如果多線程並發的訪問與一個數據結構,那么很容易破壞一個數據結構。
例如,一個線程可能要向一個散列表中插入一條數據的過程中,被剝奪了控制權。如果另外一個線程也開始遍歷同一個鏈表,很可能造成混亂,拋出異常或者陷入死循環。這就是為什么HashMap不是線程安全的原因。
一、舊的線程安全的集合
通過同步包裝器將集合變成線程安全的:
List<E> synchArrayList = Collections.synchronizedList(new ArrayList<E>()); Map<K,V> synchMap = Collections.synchronizedList(new HasMap<K,V>());
查看源代碼可以發現,就是返回了一個Collections的內部類map,這個map中所有方法都使用同步代碼塊進行了同步操作:
public static <K,V> Map<K,V> synchronizedMap(Map<K,V> m) { return new SynchronizedMap<>(m); }
private static class SynchronizedMap<K,V> implements Map<K,V>, Serializable { private static final long serialVersionUID = 1978198479659022715L; private final Map<K,V> m; // Backing Map final Object mutex; // Object on which to synchronize SynchronizedMap(Map<K,V> m) { this.m = Objects.requireNonNull(m); mutex = this; } SynchronizedMap(Map<K,V> m, Object mutex) { this.m = m; this.mutex = mutex; } public int size() { synchronized (mutex) {return m.size();} } public boolean isEmpty() { synchronized (mutex) {return m.isEmpty();} } public boolean containsKey(Object key) { synchronized (mutex) {return m.containsKey(key);} } public boolean containsValue(Object value) { synchronized (mutex) {return m.containsValue(value);} } public V get(Object key) { synchronized (mutex) {return m.get(key);} } public V put(K key, V value) { synchronized (mutex) {return m.put(key, value);} } public V remove(Object key) { synchronized (mutex) {return m.remove(key);} } public void putAll(Map<? extends K, ? extends V> map) { synchronized (mutex) {m.putAll(map);} } public void clear() { synchronized (mutex) {m.clear();} }
//省略........
}