Deprecated API

Contents

• Terminally Deprecated
• Methods

Terminally Deprecated Elements

Element	Description
java.util.concurrent.Executors.privilegedCallable(Callable<T>)	This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.
java.util.concurrent.Executors.privilegedCallableUsingCurrentClassLoader(Callable<T>)	This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.
java.util.concurrent.Executors.privilegedThreadFactory()	This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.
java.util.concurrent.ThreadPoolExecutor.finalize()

Deprecated Methods

Method	Description
java.util.concurrent.atomic.AtomicBoolean.weakCompareAndSet(boolean, boolean)	This method has plain memory effects but the method name implies volatile memory effects (see methods such as AtomicBoolean.compareAndExchange(boolean, boolean) and AtomicBoolean.compareAndSet(boolean, boolean)). To avoid confusion over plain or volatile memory effects it is recommended that the method AtomicBoolean.weakCompareAndSetPlain(boolean, boolean) be used instead.
java.util.concurrent.atomic.AtomicInteger.weakCompareAndSet(int, int)	This method has plain memory effects but the method name implies volatile memory effects (see methods such as AtomicInteger.compareAndExchange(int, int) and AtomicInteger.compareAndSet(int, int)). To avoid confusion over plain or volatile memory effects it is recommended that the method AtomicInteger.weakCompareAndSetPlain(int, int) be used instead.
java.util.concurrent.atomic.AtomicIntegerArray.weakCompareAndSet(int, int, int)	This method has plain memory effects but the method name implies volatile memory effects (see methods such as AtomicIntegerArray.compareAndExchange(int, int, int) and AtomicIntegerArray.compareAndSet(int, int, int)). To avoid confusion over plain or volatile memory effects it is recommended that the method AtomicIntegerArray.weakCompareAndSetPlain(int, int, int) be used instead.
java.util.concurrent.atomic.AtomicLong.weakCompareAndSet(long, long)	This method has plain memory effects but the method name implies volatile memory effects (see methods such as AtomicLong.compareAndExchange(long, long) and AtomicLong.compareAndSet(long, long)). To avoid confusion over plain or volatile memory effects it is recommended that the method AtomicLong.weakCompareAndSetPlain(long, long) be used instead.
java.util.concurrent.atomic.AtomicLongArray.weakCompareAndSet(int, long, long)	This method has plain memory effects but the method name implies volatile memory effects (see methods such as AtomicLongArray.compareAndExchange(int, long, long) and AtomicLongArray.compareAndSet(int, long, long)). To avoid confusion over plain or volatile memory effects it is recommended that the method AtomicLongArray.weakCompareAndSetPlain(int, long, long) be used instead.
java.util.concurrent.atomic.AtomicReference.weakCompareAndSet(V, V)	This method has plain memory effects but the method name implies volatile memory effects (see methods such as AtomicReference.compareAndExchange(V, V) and AtomicReference.compareAndSet(V, V)). To avoid confusion over plain or volatile memory effects it is recommended that the method AtomicReference.weakCompareAndSetPlain(V, V) be used instead.
java.util.concurrent.atomic.AtomicReferenceArray.weakCompareAndSet(int, E, E)	This method has plain memory effects but the method name implies volatile memory effects (see methods such as AtomicReferenceArray.compareAndExchange(int, E, E) and AtomicReferenceArray.compareAndSet(int, E, E)). To avoid confusion over plain or volatile memory effects it is recommended that the method AtomicReferenceArray.weakCompareAndSetPlain(int, E, E) be used instead.
java.util.concurrent.Executors.privilegedCallable(Callable<T>)	This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.
java.util.concurrent.Executors.privilegedCallableUsingCurrentClassLoader(Callable<T>)	This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.
java.util.concurrent.Executors.privilegedThreadFactory()	This method is only useful in conjunction with the Security Manager, which is deprecated and subject to removal in a future release. Consequently, this method is also deprecated and subject to removal. There is no replacement for the Security Manager or this method.
java.util.concurrent.ThreadPoolExecutor.finalize()