单例模式分为:
饿汉模式、懒汉模式、DCL懒汉式、静态内部类单例、枚举单例
本文逐一实现上述几种方式的单例模式,并且分析其在并发中、反射中可能出现的问题,然后对应问题给出解决方法。
一.饿汉式
1. 代码如下:
public class Hungry {
private Hungry(){
}
private static final Hungry hungry= new Hungry();
public static Hungry getInstance(){
return hungry;
}
}
2. 问题分析:
public class Hungry {
private static Byte[] bytes1 = new Byte[1024 * 1024];
private static Byte[] bytes2 = new Byte[1024 * 1024];
private static Byte[] bytes3 = new Byte[1024 * 1024];
private static Byte[] bytes4 = new Byte[1024 * 1024];
private Hungry(){
}
private static final Hungry hungry= new Hungry();
public static Hungry getInstance(){
return hungry;
}
}
饿汉式单列模式在类被加载时就会实例化一个对象,此时如果类中出现上述 new Byte[] 的情况,开辟大量内存空间,但是又不使用它,就回消耗大量内存,可能造成资源浪费。
3. 解决方法:懒汉式单例模式。
二. 懒汉式
1. 代码如下:
public class LazyMan {
private LazyMan(){
}
private static LazyMan lazyMan;
public static LazyMan getInstance(){
if (lazyMan == null){
lazyMan = new LazyMan();
}
return lazyMan;
}
}
2. 问题分析:
public class LazyMan {
private LazyMan(){
System.out.println(Thread.currentThread().getName());
}
private static LazyMan lazyMan;
public static LazyMan getInstance(){
if (lazyMan == null){
lazyMan = new LazyMan();
}
return lazyMan;
}
// 多线程并发
public static void main(String[] args) {
for (int i = 0; i < 10 ; i++) {
new Thread(() -> {
LazyMan.getInstance();
}).start();
}
}
}
第一次执行结果:
Thread-0
第二次执行结果:
Thread-1
Thread-2
Thread-0
第三次执行结果:
Thread-0
Thread-1
偶尔成功,偶尔失败,每次结果都不一样,所以在单线程没问题,并发下懒汉式单例是有问题。
3. 解决方法:
(1) 加锁:
public class LazyMan {
private LazyMan(){
System.out.println(Thread.currentThread().getName());
}
private static LazyMan lazyMan;
public static synchronized LazyMan getInstance(){
if (lazyMan == null){
lazyMan = new LazyMan();
}
return lazyMan;
}
// 多线程并发
public static void main(String[] args) {
for (int i = 0; i < 10 ; i++) {
new Thread(() -> {
LazyMan.getInstance();
}).start();
}
}
}
使用同步锁锁住了整个方法,可以解决并发问题,但是会导致效率较低;
(2) DCL懒汉式单例模式。
三. DCL懒汉式(双重检测锁模式)
1. 代码如下:
public class LazyMan {
private LazyMan(){
System.out.println(Thread.currentThread().getName());
}
private static LazyMan lazyMan;
public static LazyMan getInstance(){
if (lazyMan == null){
synchronized (LazyMan.class){ // 保证当前类只有一个
if (lazyMan == null){
lazyMan = new LazyMan();
}
}
}
return lazyMan;
}
// 多线程并发
public static void main(String[] args) {
for (int i = 0; i < 10 ; i++) {
new Thread(() -> {
LazyMan.getInstance();
}).start();
}
}
}
2. 问题分析:
(1) lazyMan = new LazyMan(),该行代码在极端情况下,是不安全的,因为它不是原子性操作;
(2) 不是原子性操作会经过哪些步骤:
1) 分配内存空间;
2) 执行构造方法,初始化对象;
3) 把这个对象指向这个空间,此时才能保证这个对象被new完了。
(3) 看上去的一步操作,其实是三步操作,此时有可能发生指令重排的现象:
1) 正常情况执行顺序是1 2 3,但是也可以变为 1 3 2,在CUP中是可以做到先分配空间,然后用空对象占用内存,占用之后再去指向对象;
2) 此时如果只有一个A线程来了,步骤1 3 2是不会出现问题的,但是如果当A线程走了步骤1 3,还没有走步骤2的时候,B线程来了,由于A线程已经走到步骤3了,此时B线程就会认定 lazyMan != null,此时就会直接return lazyMan,但是此时还未走步骤2,也就是说 lazyMan 还没有完成构造,就会出现线程安全问题。
3. 解决方法:
添加volatile避免指令重排,代码如下:
public class LazyMan {
private LazyMan(){
System.out.println(Thread.currentThread().getName());
}
private volatile static LazyMan lazyMan;
public static LazyMan getInstance(){
if (lazyMan == null){
synchronized (LazyMan.class){ // 保证当前类只有一个
if (lazyMan == null){
lazyMan = new LazyMan();
}
}
}
return lazyMan;
}
// 多线程并发
public static void main(String[] args) {
for (int i = 0; i < 10 ; i++) {
new Thread(() -> {
LazyMan.getInstance();
}).start();
}
}
}
四. 静态内部类式
1. 代码如下:
public class Holder {
private Holder(){
}
public static Holder getInstance(){
return InnerClass.holder;
}
public static class InnerClass{
private static final Holder holder = new Holder();
}
}
这种方式感觉很厉害,花里胡哨的,但是没有多大真实的作用。
五. 反射破解单例
上述4种单例其实都是不安全的,都可以通过反射进行破解,如下通过懒汉式进行破解分析:
1. 代码如下:
public class LazyMan {
private LazyMan(){
System.out.println(Thread.currentThread().getName());
}
private volatile static LazyMan lazyMan;
public static LazyMan getInstance(){
if (lazyMan == null){
synchronized (LazyMan.class){ // 保证当前类只有一个
if (lazyMan == null){
lazyMan = new LazyMan();
}
}
}
return lazyMan;
}
// 反射破解
public static void main(String[] args) throws Exception {
LazyMan instance1 = LazyMan.getInstance();
Constructor<LazyMan> declaredConstructor = LazyMan.class.getDeclaredConstructor(null);
declaredConstructor.setAccessible(true);
LazyMan instance2 = declaredConstructor.newInstance();
System.out.println("懒汉式创建的lazyMan:"+instance1);
System.out.println("反射创建的lazyMan:"+instance2);
}
}
执行结果:
main
main
懒汉式创建的lazyMan:com.juc.single.LazyMan@14ae5a5
反射创建的lazyMan:com.juc.single.LazyMan@7f31245a
通过结果明显发现不是一个对象。
2. 第一次解决:
public class LazyMan {
private LazyMan(){
synchronized (LazyMan.class){
if (lazyMan != null){
throw new RuntimeException("禁止反射破坏异常");
}
}
System.out.println(Thread.currentThread().getName());
}
private volatile static LazyMan lazyMan;
public static LazyMan getInstance(){
if (lazyMan == null){
synchronized (LazyMan.class){ // 保证当前类只有一个
if (lazyMan == null){
lazyMan = new LazyMan();
}
}
}
return lazyMan;
}
// 反射破解
public static void main(String[] args) throws Exception {
LazyMan instance1 = LazyMan.getInstance();
Constructor<LazyMan> declaredConstructor = LazyMan.class.getDeclaredConstructor(null);
declaredConstructor.setAccessible(true);
LazyMan instance2 = declaredConstructor.newInstance();
System.out.println("懒汉式创建的lazyMan:"+instance1);
System.out.println("反射创建的lazyMan:"+instance2);
}
}
执行结果:
main
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.juc.single.LazyMan.main(LazyMan.java:34)
Caused by: java.lang.RuntimeException: 禁止反射破坏异常
at com.juc.single.LazyMan.<init>(LazyMan.java:10)
... 5 more
此时将双重锁检索升级成为三重锁检索避免反射的某一种破坏,但是如果两个对象都是反射创建的情况下,同样可以破解,代码如下:
public class LazyMan {
private LazyMan(){
synchronized (LazyMan.class){
if (lazyMan != null){
throw new RuntimeException("禁止反射破坏异常");
}
}
System.out.println(Thread.currentThread().getName());
}
private volatile static LazyMan lazyMan;
public static LazyMan getInstance(){
if (lazyMan == null){
synchronized (LazyMan.class){ // 保证当前类只有一个
if (lazyMan == null){
lazyMan = new LazyMan();
}
}
}
return lazyMan;
}
// 反射破解
public static void main(String[] args) throws Exception {
Constructor<LazyMan> declaredConstructor = LazyMan.class.getDeclaredConstructor(null);
declaredConstructor.setAccessible(true);
LazyMan instance1 = declaredConstructor.newInstance();
LazyMan instance2 = declaredConstructor.newInstance();
System.out.println("反射创建的lazyMan1:"+instance1);
System.out.println("反射创建的lazyMan2:"+instance2);
}
}
执行结果:
main
main
反射创建的lazyMan1:com.juc.single.LazyMan@14ae5a5
反射创建的lazyMan2:com.juc.single.LazyMan@7f31245a
通过结果明显发现不是一个对象。
3. 第二次解决:
public class LazyMan {
private static boolean jingZhiFanShe = false;
private LazyMan(){
synchronized (LazyMan.class){
if (jingZhiFanShe == false){
jingZhiFanShe = true;
}else{
throw new RuntimeException("禁止反射破坏异常");
}
}
System.out.println(Thread.currentThread().getName());
}
private volatile static LazyMan lazyMan;
public static LazyMan getInstance(){
if (lazyMan == null){
synchronized (LazyMan.class){ // 保证当前类只有一个
if (lazyMan == null){
lazyMan = new LazyMan();
}
}
}
return lazyMan;
}
// 反射破解
public static void main(String[] args) throws Exception {
Constructor<LazyMan> declaredConstructor = LazyMan.class.getDeclaredConstructor(null);
declaredConstructor.setAccessible(true);
LazyMan instance1 = declaredConstructor.newInstance();
LazyMan instance2 = declaredConstructor.newInstance();
System.out.println("反射创建的lazyMan1:"+instance1);
System.out.println("反射创建的lazyMan2:"+instance2);
}
}
执行结果:
main
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.juc.single.LazyMan.main(LazyMan.java:38)
Caused by: java.lang.RuntimeException: 禁止反射破坏异常
at com.juc.single.LazyMan.<init>(LazyMan.java:14)
... 5 more
此时通过标志位判断避免反射的某一种破坏,如果不通过反编译,是无法找到该关键字的,如果对关键字做一些加密,就会使创建单例变的更安全,但是再安全的加密也会被解密,代码如下:
public class LazyMan {
private static boolean jingZhiFanShe = false;
private LazyMan(){
synchronized (LazyMan.class){
if (jingZhiFanShe == false){
jingZhiFanShe = true;
}else{
throw new RuntimeException("禁止反射破坏异常");
}
}
System.out.println(Thread.currentThread().getName());
}
private volatile static LazyMan lazyMan;
public static LazyMan getInstance(){
if (lazyMan == null){
synchronized (LazyMan.class){ // 保证当前类只有一个
if (lazyMan == null){
lazyMan = new LazyMan();
}
}
}
return lazyMan;
}
// 反射破解
public static void main(String[] args) throws Exception {
Field field = LazyMan.class.getDeclaredField("jingZhiFanShe");
field.setAccessible(true);
Constructor<LazyMan> declaredConstructor = LazyMan.class.getDeclaredConstructor(null);
declaredConstructor.setAccessible(true);
LazyMan instance1 = declaredConstructor.newInstance();
field.set(instance1,false);// 将jingZhiFanShe的值改为false
LazyMan instance2 = declaredConstructor.newInstance();
System.out.println("反射创建的lazyMan1:"+instance1);
System.out.println("反射创建的lazyMan2:"+instance2);
}
}
通过修改关键字进行破解。
4. 分析newInstance源码:
@CallerSensitive
public T newInstance(Object ... initargs)
throws InstantiationException, IllegalAccessException,
IllegalArgumentException, InvocationTargetException
{
if (!override) {
if (!Reflection.quickCheckMemberAccess(clazz, modifiers)) {
Class<?> caller = Reflection.getCallerClass();
checkAccess(caller, clazz, null, modifiers);
}
}
// 如果类型是枚举类型,会报错"不能使用反射破坏枚举"
if ((clazz.getModifiers() & Modifier.ENUM) != 0)
throw new IllegalArgumentException("Cannot reflectively create enum objects");
ConstructorAccessor ca = constructorAccessor; // read volatile
if (ca == null) {
ca = acquireConstructorAccessor();
}
@SuppressWarnings("unchecked")
T inst = (T) ca.newInstance(initargs);
return inst;
}
通过源码分析,可以通过枚举方式替换自定义标志位解决。
5. 枚举分析:
(1) 编写枚举类:
public enum EnumSingle {
INSTANCE;
public EnumSingle getInstance(){
return INSTANCE;
}
}
(2) 直接Idea中分析EmunSingle.class文件:
public enum EnumSingle {
INSTANCE;
private EnumSingle() {
}
public EnumSingle getInstance() {
return INSTANCE;
}
}
从Idea中查看EmunSingle的class文件发现,EmunSingle有一个无参构造器。
(3) 编写测试类:
public enum EnumSingle {
INSTANCE;
public EnumSingle getInstance(){
return INSTANCE;
}
}
class Test{
public static void main(String[] args) throws Exception {
EnumSingle instance1 = EnumSingle.INSTANCE;
Constructor<EnumSingle> declaredConstructor = EnumSingle.class.getDeclaredConstructor(null);
declaredConstructor.setAccessible(true);
EnumSingle instance2 = declaredConstructor.newInstance();
System.out.println("反射创建的EnumSingle1:"+instance1);
System.out.println("反射创建的EnumSingle2:"+instance2);
}
}
执行结果:
Exception in thread "main" java.lang.NoSuchMethodException: com.juc.single.EnumSingle.<init>()
at java.lang.Class.getConstructor0(Class.java:3082)
at java.lang.Class.getDeclaredConstructor(Class.java:2178)
at com.juc.single.Test.main(EnumSingle.java:16)
此报错说没有该方法,和newInstance源码中的"Cannot reflectively create enum objects"不相符,因为代码的执行结果肯定是不会有问题的,所以说明该class文件是有问题的。
(4) 通过javap分析EmunSingle.class文件:
public final class com.juc.single.EnumSingle extends java.lang.Enum<com.juc.single.EnumSingle> {
public static final com.juc.single.EnumSingle INSTANCE;
private static final com.juc.single.EnumSingle[] $VALUES;
public static com.juc.single.EnumSingle[] values();
public static com.juc.single.EnumSingle valueOf(java.lang.String);
private com.juc.single.EnumSingle();
public com.juc.single.EnumSingle getInstance();
static {};
}
通过javap -p EnumSingle.class命令查看EmunSingle的class,发现还是一个无参构造器,也是有问题的,那就需要更专业的工具(jad)进行分析。
(5) 通过jad分析EmunSingle.class文件:
public final class EnumSingle extends Enum
{
public static EnumSingle[] values()
{
return (EnumSingle[])$VALUES.clone();
}
public static EnumSingle valueOf(String name)
{
return (EnumSingle)Enum.valueOf(com/juc/single/EnumSingle, name);
}
private EnumSingle(String s, int i)
{
super(s, i);
}
public EnumSingle getInstance()
{
return INSTANCE;
}
public static final EnumSingle INSTANCE;
private static final EnumSingle $VALUES[];
static
{
INSTANCE = new EnumSingle("INSTANCE", 0);
$VALUES = (new EnumSingle[] {
INSTANCE
});
}
}
通过jad -sjava EnumSingle.class命令还原EnumSingle.java文件,可以发现EnumSingle是一个有两个参数的构造器。
(6) 重写编写测试类:
public enum EnumSingle {
INSTANCE;
public EnumSingle getInstance(){
return INSTANCE;
}
}
class Test{
public static void main(String[] args) throws Exception {
EnumSingle instance1 = EnumSingle.INSTANCE;
Constructor<EnumSingle> declaredConstructor = EnumSingle.class.getDeclaredConstructor(String.class,int.class);
declaredConstructor.setAccessible(true);
EnumSingle instance2 = declaredConstructor.newInstance();
System.out.println("反射创建的EnumSingle1:"+instance1);
System.out.println("反射创建的EnumSingle2:"+instance2);
}
}
执行结果:
Exception in thread "main" java.lang.IllegalArgumentException: Cannot reflectively create enum objects
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at com.juc.single.Test.main(EnumSingle.java:18)
此时的报错符合我们的预期,证明反射不能破坏枚举的单例。
六. 枚举式
代码如下:
public enum EnumSingleTest {
INSTANCE;
public EnumSingleTest getInstance(){
return INSTANCE;
}
}
class EnumTest{
public static void main(String[] args) {
EnumSingleTest instance = EnumSingleTest.INSTANCE.getInstance();
System.out.println(instance);
}
}
推荐使用枚举式单例,利用枚举的特性,让JVM来帮我们保证线程安全和单一实例的问题,并且写法还非常简单;
直接通过EnumSingleTest.INSTANCE.getInstance()的方式调用即可。
PS:该文档为【狂神说Java】JUC并发编程最新版通俗易懂_哔哩哔哩_bilibili 中单例模式的学习笔记,推荐想快速理解例模式的去B站学习。