单例模式用于生产全局唯一的对象。常见有懒汉式、饿汉式、内部类、双重检查、枚举式。
代码
// 饿汉式 (jvm 保证线程安全)
class Single {
private final static Single instance = new Single();
private Single(){}
public static Single getSingleInstance(){
return instance;
}
}
// 结果测试
public static void main(String[] args) {
for (int i = 0; i < 100; i++) {
new Thread(new Runnable() {
@Override
public void run() {
System.out.println(Thread.currentThread().getId()+"===>"+Single.getSingleInstance().hashCode());
}
}).start();
}
}
// 懒汉式(双重检查 通过锁保证线程安全)
class Single {
private static volatile Single instance;
private Single(){}
public static Single getSingleInstance(){
if(instance==null){
synchronized (Single.class){
if(instance==null){
instance = new Single();
}
}
}
return instance;
}
}
//懒汉式 (静态内部类 jvm 保证线程安全)
class Single {
private Single(){}
static class SingleSon{
private final static Single instance = new Single();
}
public static Single getSingleInstance(){
return SingleSon.instance;
}
}
//枚举类 (jvm 保证线程安全)
enum Single{
INSTANCE;
public void doSomeThing(){
System.out.println("this is single object");
}
}
======================================================================
以上能保证线程安全 但是由于java 中存在反射机制 除了枚举类 以上三种均可被破坏(当然也有对应的解决方案)
Constructor declaredConstructor = Single.class.getDeclaredConstructor();
declaredConstructor.setAccessible(true);
Single single1 = (Single) declaredConstructor.newInstance();
Single single2 = Single.getInstance();
System.out.println((single1 == single2));
===========================================================
思考:
为什么加 volatile? 为什么双重检查?枚举不会被反射破坏的原因?