When singleton can break and how to resolve it

Javasearch.buggybread.com

Search Interview Questions

More than 3000 questions in repository.

There are more than 900 unanswered questions.
Click here and help us by providing the answer.

Have a video suggestion.
Click Correct / Improve and please let us know.

Submit Question

Interview Questions and Answers

Q1. When singleton can break and how to resolve it

Ans. Deserialization. In serialization, we can save the object of a byte stream into a file or send over a network. Suppose if you serialize the Singleton class, and then again de-serialize that object, it will create a new instance, hence deserialization will break the Singleton pattern.

To overcome this issue, we need to override readResolve() method in the Singleton class and return the same Singleton instance.

Help us improve. Please let us know the company, where you were asked this question :

_{Like Discuss Correct / Improve singleton design patterns Asked in 1 Companies}

Related Questions

Difference between Static and Singleton Class ?

What is the difference between these two approaches of creating singleton Class ?

//Double Checked Locking Code
public static Singleton createInstance() {
   if(singleton == null){
      synchronized(Singleton.class) {
         if(singleton == null) {
            singleton = new Singleton();
         }
      }
   }
   return singleton;
}

//Single checked locking code
public static Singleton createInstance() {
   synchronized(Singleton.class) {
      if(singleton == null) {
         singleton = new Singleton();
      }
   }
   return singleton;
}

What is the difference between Singleton and Prototype Bean scope in Spring ?

serialization and deserialization of singleton class

How to avoid cloning, serialization in the singleton class ?

If you are given choice to either load object eagerly or lazily , which one would you use in case of singleton pattern ?

When should we use prototype scope and singleton scope for beans ?

Explain Singleton Design Pattern ?

Shouldn't we make a class with all static members is its just expected to be executed as a standalone program with just one thread. Moreover Lets assume that there is no runtime Polymorphism required and there is no need for serialization ?