Core Java Interview Questions
PS: If you like the page or have any questions, feel free to comment at end.
Ans) The ability to define a function in multiple forms is called Polymorphism. In java, c++ there are two types of polymorphism: compile time polymorphism (overloading) and runtime polymorphism (overriding).
Method overriding: happens when a child class implements the method with the same signature as a method in a parent class. When you override methods, JVM determines the proper methods to call at the programвЂ™s runtime, not at the compile time.
Method overloading: happens when several methods have same names but different number or type of parameters. Overloading is determined at the compile time.
- Overloading happens when:
- Different method signature and different number or type of parameters.
- Same method signature but different number of parameters.
- Same method signature and same number of parameters but of different type
Example of Overloading
Q) What is the use of serialVersionUID?
Ans) The default Java serialization mechanism writes the metadata about the object, which includes the class name, field name, types, and superclass. This class definition is stored as a part of the serialized object. This stored metadata enables the deserialization process to reconstitute the objects and map the stream data into the class attributes with the appropriate type.
Everytime an object is serialized the java serialization mechanism automatically computes a hash value. ObjectStreamClass’s computeSerialVersionUID() method passes the class name, sorted member names, modifiers, and interfaces to the secure hash algorithm (SHA), which returns a hash value.The serialVersionUID is also called suid. So when the serialized object is retrieved, the JVM first evaluates the suid of the serialized class and compares the suid value with the one of the objects. If the suid values match then the object is said to be compatible with the class and hence it is de-serialized, if not InvalidClassException exception is thrown.
Changes to a serializable class can be compatible or incompatible. Following is the list of changes which are compatible:
- Add fields
- Change a field from static to non-static
- Change a field from transient to non-transient
- Add classes to the object tree
List of incompatible changes:
- Delete fields
- Change class hierarchy
- Change non-static to static
- Change non-transient to transient
- Change type of a primitive field
If no suid is present, when making compatible changes, jvm generates new suid thus resulting in an exception if prior release version object is used.
The only way to get rid of the exception is to recompile and deploy the application again.
If we explicitly mention the suid using the statement:
then if any of the metioned compatible changes are made the class need not to be recompiled. But for incompatible changes there is no other way than to compile again.
Q) What is the difference between final, finally and finalize() in Java?
Ans) final – A final variable acts as a constant, a final class is immutable and a final method cannot be overriden in a child class.
finally – finally keyword is used with try-catch block for handling exceptions. The finally block is optional in try-catch block. The finally code block is always executed after try or catch block is completed. The finally block is mainly executed to close the resources or clean up objects used in the try block. For e.g. Closing a FileStream, I/O stream objects, Database connections, HTTP connections are generally closed in a finally block.
finalize() – This is the method of Object class.It is invoked before an object is discarded by the garbage collector, allowing it to clean up its state. Should not be used to release non-memory resources like file handles, sockets, database connections etc because Java has only a finite number of these resources and you do not know when the garbage collection is going to kick in to release these non-memory resources through the finalize() method.
Q4)What is the difference between HashMap and HashTable?
Ans) Both collections implements Map. Both collections store value as key-value pairs. The key differences between the two are:
- Hashmap is not synchronized in nature but hashtable is(thread-safe). This means that in a multithreaded application, only one thread can get access to a hashtable object and do an operation on it. Hashmap doesn’t gurantee such behavior and is not used in multithreaded environment.
- Hashmap is traveresed using an iterator, hashtable can be traversed by enumerator or iterator.
- Iterator in hashmap is fail-fast, enumerator in hashtable is not fail-fast
- HashMap permits null values and only one null key, while Hashtable doesn’t allow key or value as null.
- Since hashtable is synchornized, it is relatively slower in performance than hashmap
Q) What is the difference between abstract class and interface ?
Ans) A class is called abstract when it is declared with the keyword abstract . Abstract class contains at least one abstract method. It can also contain n numbers of concrete method. An interface can only contain abstract methods.
- An interface can have only abstract methods. Abstract class can have concrete and abstract methods.
- The abstract class can have public, private, protected or default variables and also constants. In interface the variable is by default public final. In nutshell the interface doesn’t have any variables it only has constants.
- A class can extend only one abstract class but a class can implement multiple interfaces. Abstract class doesn’t support multiple inheritance whereas abstract class does.
- If an interface is implemented its mandatory to implement all of its methods but if an abstract class is extended its mandatory to implement all abstract methods.
- The problem with an interface is, if you want to add a new feature (method) in its contract, then you MUST implement the new method(s) in all of the classes which implement that interface. However, in the case of an abstract class, the method can be simply implemented in the abstract class and the same can be called by its subclass.
Q) What is the difference between equals() and == ?
Ans) == operator is used to compare the references of the objects.
public boolean equals(Object o) is the method provided by the Object class. The default implementation uses == operator to compare two objects which mean by default the objects address are compared. But since the method can be overriden like for String class. equals() method can be used to compare the values of two objects.
Q) What is difference between a thread and a process?
- Threads share the address space of the process that created it; process has it’s own address space.
- Threads have direct access to the data segment of its process; processes have their own copy of the data segment of the parent process.
- Threads can directly communicate with other threads of its process; processes must use interprocess communication to communicate with sibling processes.
- Threads have almost no overhead; processes have considerable overhead.
- New threads are easily created; new processes require duplication of the parent process.
- Threads can exercise considerable control over threads of the same process; processes can only exercise control over child processes.
- Changes to the main thread (cancellation, priority change etc.) may affect the behavior of the other threads of the process; changes to the parent process do not affect child processes.
Q) What is the use of synchronized keyword?
Ans) synchronized keyword can be applied to static/non-static methods or a block of code. Only one thread at a time can access synchronized methods and if there are multiple threads trying to access the same method other threads have to wait until current thread finishes the execution and release lock. Synchronized keyword provides a lock on the object and thus prevents race condition. E.g.
Q)Is garbage collector a daemon thread?
Ans) Yes GC is a daemon thread. A daemon thread runs behind the application. It is started by JVM. The thread stops when all non-daemon threads stop.
Q)How is Garbage Collection managed?
Ans)The JVM controls the Garbage Collector; it decides when to run the Garbage Collector. JVM runs the Garbage Collector when it realizes that the memory is running low. The behavior of GC can be tuned by passing parameters to JVM. One can request the Garbage Collection to happen from within the java program but there is no guarantee that this request will be taken care of by jvm.