By Ziggy


2008-10-20 13:18:09 8 Comments

What are Null Pointer Exceptions (java.lang.NullPointerException) and what causes them?

What methods/tools can be used to determine the cause so that you stop the exception from causing the program to terminate prematurely?

12 comments

@OscarRyz 2008-10-20 20:05:30

In Java all the variables you declare are actually "references" to the objects (or primitives) and not the objects themselves.

When you attempt to execute one object method, the reference asks the living object to execute that method. But if the reference is referencing NULL (nothing, zero, void, nada) then there is no way the method gets executed. Then the runtime let you know this by throwing a NullPointerException.

Your reference is "pointing" to null, thus "Null -> Pointer".

The object lives in the VM memory space and the only way to access it is using this references. Take this example:

public class Some {
    private int id;
    public int getId(){
        return this.id;
    }
    public setId( int newId ) {
        this.id = newId;
    }
}

And on another place in your code:

Some reference = new Some();    // Point to a new object of type Some()
Some otherReference = null;     // Initiallly this points to NULL

reference.setId( 1 );           // Execute setId method, now private var id is 1

System.out.println( reference.getId() ); // Prints 1 to the console

otherReference = reference      // Now they both point to the only object.

reference = null;               // "reference" now point to null.

// But "otherReference" still point to the "real" object so this print 1 too...
System.out.println( otherReference.getId() );

// Guess what will happen
System.out.println( reference.getId() ); // :S Throws NullPointerException because "reference" is pointing to NULL remember...

This an important thing to know - when there are no more references to an object (in the example above when reference and otherReference both point to null) then the object is "unreachable". There is no way we can work with it, so this object is ready to be garbage collected, and at some point, the VM will free the memory used by this object and will allocate another.

@ashish bhatt 2012-01-28 06:45:54

In Java, everything is in the form of a class.

If you want to use any object then you have two phases:

  1. Declare
  2. Initialization

Example:

  • Declaration: Object a;
  • Initialization: a=new Object();

Same for the array concept

  • Declaration: Item i[]=new Item[5];
  • Initialization: i[0]=new Item();

If you are not giving the initialization section then the NullpointerException arise.

@Michael Krause 2016-11-15 21:44:02

Declaring a primitive variable, such as an int, in Java does not create an Object.

@sunhang 2017-07-28 10:25:10

A NullPointerException often occurs when calling method of an instance.For example, if you declare a reference but does not make it point to any instance, NullPointerException will happen when you call its method. such as: YourClass ref = null; // or ref = anotherRef; // but anotherRef has not pointed any instance ref.someMethod(); // it will throw NullPointerException. Generally fix it in this way: Before the method is called, determine whether the reference is null. such as: if (yourRef != null) { yourRef.someMethod(); }

@sunhang 2017-07-28 10:25:14

Or use exception capture: such as: try { yourRef.someMethod(); } catch (NullPointerException e) { // TODO }

@Jorge Ferreira 2008-10-20 13:21:21

It's like you are trying to access an object which is null. Consider below example:

TypeA objA;

At this time you have just declared this object but not initialized or instantiated. And whenever you try to access any property or method in it, it will throw NullPointerException which makes sense.

See this below example as well:

String a = null;
System.out.println(a.toString()); // NullPointerException will be thrown

@Vincent Ramdhanie 2008-10-20 13:54:24

When you declare a reference variable (i.e. an object) you are really creating a pointer to an object. Consider the following code where you declare a variable of primitive type int:

int x;
x = 10;

In this example, the variable x is an int and Java will initialize it to 0 for you. When you assign it to 10 in the second line your value 10 is written into the memory location pointed to by x.

But, when you try to declare a reference type something different happens. Take the following code:

Integer num;
num = new Integer(10);

The first line declares a variable named num, but, it does not contain a primitive value. Instead, it contains a pointer (because the type is Integer which is a reference type). Since you did not say as yet what to point to Java sets it to null, meaning "I am pointing at nothing".

In the second line, the new keyword is used to instantiate (or create) an object of type Integer and the pointer variable num is assigned this object. You can now reference the object using the dereferencing operator . (a dot).

The Exception that you asked about occurs when you declare a variable but did not create an object. If you attempt to dereference num BEFORE creating the object you get a NullPointerException. In the most trivial cases, the compiler will catch the problem and let you know that "num may not have been initialized" but sometimes you write code that does not directly create the object.

For instance, you may have a method as follows:

public void doSomething(SomeObject obj) {
   //do something to obj
}

In which case you are not creating the object obj, rather assuming that it was created before the doSomething method was called. Unfortunately, it is possible to call the method like this:

doSomething(null);

In which case obj is null. If the method is intended to do something to the passed-in object, it is appropriate to throw the NullPointerException because it's a programmer error and the programmer will need that information for debugging purposes.

Alternatively, there may be cases where the purpose of the method is not solely to operate on the passed in object, and therefore a null parameter may be acceptable. In this case, you would need to check for a null parameter and behave differently. You should also explain this in the documentation. For example, doSomething could be written as:

/**
  * @param obj An optional foo for ____. May be null, in which case 
  *  the result will be ____.
  */
public void doSomething(SomeObject obj) {
    if(obj != null) {
       //do something
    } else {
       //do something else
    }
}

Finally, How to pinpoint the exception & cause using Stack Trace

@Boann 2014-07-29 13:32:07

"The best way to avoid this type of exception is to always check for null when you did not create the object yourself." If the caller passes null, but null is not a valid argument for the method, then it's correct to throw the exception back at the caller because it's the caller's fault. Silently ignoring invalid input and doing nothing in the method is extremely poor advice because it hides the problem.

@Simon Fischer 2014-09-26 19:45:00

I would add a remark about this post explaining that even assignments to primitives can cause NPEs when using autoboxing: int a=b can throw an NPE if b is an Integer. There are cases where this is confusing to debug.

@Sid 2015-04-13 14:51:23

Is it possible to capture NPE thrown by a webapp from the web browser?like will it show in the view page source from the web browser..

@Rose 2015-11-11 04:39:16

Yes check if the object equals null before you invoke a method on it or try to access a variable it might have. Some times structuring your code can help avoid null pointer exception. eg when checking an input string with a constant string you should start with the constant string like here: if ("SomeString".equals(inputString)) {} //even if inputString is null no exception is thrown. So there are a bunch of things that you can do to try to be safe.

@Razvan Manolescu 2015-12-20 15:02:44

Another small addition is to try to use Optional return types if it's not mandatory for our logic to not return values, if we want to force a check in the caller.

@Arjan Mels 2016-01-03 18:17:34

An additional way of avoiding NullPointerException problems in your code is to use @Nullable and @NotNull annotations. The following answer has more information on this. Although this answer is specificially about the IntelliJ IDE, it is also applicable to other tools as is apparanet from teh comments. (BTW I am not allowed to edit this answer directly, perhaps the author can add it?)

@wvdz 2016-03-16 16:05:16

Downvoted because it's not true that Java sets a variable to its default value if you declare it within a method. It only does this with instance variables. If you declare a variable within a method without assigning it a value, and then try to use it, you will get the variable may not be initialized compiler error.

@Tenfour04 2016-08-02 19:40:03

@Boann The example doesn't make sense to begin with, since Integer is an immutable type. You can't "do something to num".

@Elazar 2016-08-03 16:10:29

A pointer is a primitive value, of a primitive type. It's the pointee that isn't.

@John Vandivier 2017-03-17 15:42:24

Another common root cause of NPE is to create an object from a query and call properties on that object without checking if it is empty. Eg: Document document = repo.getDocumentSetByFilter(filter).get(0).getFirstDocument(‌​); Here an NPE can be fixed by performing an empty check after .get(0) and before .getFirstDocument();

@Tom O. 2017-07-13 15:47:02

Also, I think it's important to clarify that NullPointerException is an unchecked exception as opposed to a checked exception. This is a good starting place to start learning the difference between checked and unchecked exceptions.

@A.Shaheri 2017-07-30 07:23:21

good explanation but sometimes it's not a good practice to handle this exception by if and else, consider a service that you're providing: it would be better if you let the consumer know that the request causes a null pointer exception. Sometimes handling these events by throwing a proper exception would be more useful.

@MC Emperor 2017-10-02 07:01:54

@Vincent Maybe you could add that a NullPointerException is sometimes thrown when auto-unboxing takes place: Boolean b; and then if (b) { ... }. It sometimes confuses newbies.

@Aguid 2017-10-25 09:57:26

what about using Null Object Design Pattern ? when it is recommended ?

@Roland 2017-11-10 10:39:34

General advice to NPEs: On public/package/protected methods, do always validate any incoming parameter on null and include a developer-friendly message: if (null == someParameter) { throw new NullPointerException("someParameter is null");` If someParameter is a DAO, and I know it **must** be fully persisted when handled over, I also check it's primary key below above general check: if (someParameter.getSomeId() == null) { throw new NullPointerException("someParameter.someId is null");`.

@Roland 2017-11-10 10:40:43

And to make sure, the id is never below one: if (someParameter.getSomeId() < 1) { throw new IllegalArgumentException("someParameter.someId="+someParamet‌​er.getSomeId()+" is invalid"); This way, I make sure that my public/package/protected (not private, as this makes unit-testing much harder) are properly invoked.

@Hasindu Gajanayake 2018-02-08 08:03:46

NullPointerException is thrown when an application attempts to use an object reference that has the null value. These include: Calling an instance method on the object referred by a null reference. Accessing or modifying an instance field of the object referred by a null reference. If the reference type is an array type, taking the length of a null reference. If the reference type is an array type, accessing or modifying the slots of a null reference. If the reference type is a subtype of Throwable, throwing a null reference.

@Yatin Makkad 2018-02-19 16:39:10

When you access some property of an object on null reference, then NullPointerException is thrown.

@Xtroce 2018-03-23 22:03:23

One interesting aspect to "prevent" NullPointerExceptions from happening since Java 8 is the Optional<T> class. If misused it does not prevent it but if used correctly it can help enourmously by enforcing checks on places where null may be passed by methods. The idea behind it is that it wraps around the actual object that you are passing and provides an isPresent method to check whether a vaiable is present or not. Although this could be done by an != null check, the advantage is the clarity that if you see that an Optional is returned by a method, you instantly know it can be null.

@Frans 2018-04-18 07:29:39

Downvoted because it is factually incorrect that between declaring the local variable num and assigning an Integer reference to it, its value would be null. In fact, its value is unassigned, and trying to use it is a compile-time error. Instance variables get initialized to null when an object is created, but the above example seems to be about a local variable.

@AtulJain 2018-09-25 18:17:53

If you are using jdk8 then would suggest ofNullable API. opt = Optional.ofNullable(null); assertFalse(opt.isPresent());

@software.wikipedia 2019-01-08 22:53:38

Surprisingly nobody mentioned static code analysis here. IntelliJ, Eclipse and find bugs do help identify these during development. Steps r here: fromdev.com/2018/02/good-bye-nullpointerexception-in-java.ht‌​ml

@Stephen C 2014-06-22 02:16:56

Question: What causes a NullPointerException (NPE)?

As you should know, Java types are divided into primitive types (boolean, int, etc.) and reference types. Reference types in Java allow you to use the special value null which is the Java way of saying "no object".

A NullPointerException is thrown at runtime whenever your program attempts to use a null as if it was a real reference. For example, if you write this:

public class Test {
    public static void main(String[] args) {
        String foo = null;
        int length = foo.length();   // HERE
    }
}

the statement labelled "HERE" is going to attempt to run the length() method on a null reference, and this will throw a NullPointerException.

There are many ways that you could use a null value that will result in a NullPointerException. In fact, the only things that you can do with a null without causing an NPE are:

  • assign it to a reference variable or read it from a reference variable,
  • assign it to an array element or read it from an array element (provided that array reference itself is non-null!),
  • pass it as a parameter or return it as a result, or
  • test it using the == or != operators, or instanceof.

Question: How do I read the NPE stacktrace?

Suppose that I compile and run the program above:

$ javac Test.java 
$ java Test
Exception in thread "main" java.lang.NullPointerException
    at Test.main(Test.java:4)
$

First observation: the compilation succeeds! The problem in the program is NOT a compilation error. It is a runtime error. (Some IDEs may warn your program will always throw an exception ... but the standard javac compiler doesn't.)

Second observation: when I run the program, it outputs two lines of "gobbledy-gook". WRONG!! That's not gobbledy-gook. It is a stacktrace ... and it provides vital information that will help you track down the error in your code, if you take the time to read it carefully.

So let's look at what it says:

Exception in thread "main" java.lang.NullPointerException

The first line of the stack trace tells you a number of things:

  • It tells you the name of the Java thread in which the exception was thrown. For a simple program with one thread (like this one), it will be "main". Let's move on ...
  • It tells you the full name of the exception that was thrown; i.e. java.lang.NullPointerException.
  • If the exception has an associated error message, that will be output after the exception name. NullPointerException is unusual in this respect, because it rarely has an error message.

The second line is the most important one in diagnosing an NPE.

at Test.main(Test.java:4)

This tells us a number of things:

  • "at Test.main" says that we were in the main method of the Test class.
  • "Test.java:4" gives the source filename of the class, AND it tells us that the statement where this occurred is in line 4 of the file.

If you count the lines in the file above, line 4 is the one that I labeled with the "HERE" comment.

Note that in a more complicated example, there will be lots of lines in the NPE stack trace. But you can be sure that the second line (the first "at" line) will tell you where the NPE was thrown1.

In short the stack trace will tell us unambiguously which statement of the program has thrown the NPE.

1 - Not quite true. There are things called nested exceptions...

Question: How do I track down the cause of the NPE exception in my code?

This is the hard part. The short answer is to apply logical inference to the evidence provided by the stack trace, the source code and the relevant API documentation.

Let's illustrate with the simple example (above) first. We start by looking at the line that the stack trace has told us is where the NPE happened:

int length = foo.length(); // HERE

How can that throw an NPE?

In fact there is only one way: it can only happen if foo has the value null. We then try to run the length() method on null and .... BANG!

But (I hear you say) what if the NPE was thrown inside the length() method call?

Well, if that happened, the stack trace would look different. The first "at" line would say that the exception was thrown in some line in the java.lang.String class, and line 4 of Test.java would be the second "at" line.

So where did that null come from? In this case it is obvious, and it is obvious what we need to do to fix it. (Assign a non-null value to foo.)

OK, so let's try a slightly more tricky example. This will require some logical deduction.

public class Test {

    private static String[] foo = new String[2];

    private static int test(String[] bar, int pos) {
        return bar[pos].length();
    }

    public static void main(String[] args) {
        int length = test(foo, 1);
    }
}

$ javac Test.java 
$ java Test
Exception in thread "main" java.lang.NullPointerException
    at Test.test(Test.java:6)
    at Test.main(Test.java:10)
$ 

So now we have two "at" lines. The first one is for this line:

return args[pos].length();

and the second one is for this line:

int length = test(foo, 1);

Looking at the first line, how could that throw an NPE? There are two ways:

  • If the value of bar is null then bar[pos] will throw an NPE.
  • If the value of bar[pos] is null then calling length() on it will throw an NPE.

Next, we need to figure out which of those scenarios explains what is actually happening. We will start by exploring the first one:

Where does bar come from? It is a parameter to the test method call, and if we look at how test was called, we can see that it comes from the foo static variable. In addition, we can see clearly that we initialized foo to a non-null value. That is sufficient to tentatively dismiss this explanation. (In theory, something else could change foo to null ... but that is not happening here.)

So what about our second scenario? Well, we can see that pos is 1, so that means that foo[1] must be null. Is that possible?

Indeed it is! And that is the problem. When we initialize like this:

private static String[] foo = new String[2];

we allocate a String[] with two elements that are initialized to null. After that, we have not changed the contents of foo ... so foo[1] will still be null.

@fgb 2014-06-07 19:22:14

What is a NullPointerException?

A good place to start is the JavaDocs. They have this covered:

Thrown when an application attempts to use null in a case where an object is required. These include:

  • Calling the instance method of a null object.
  • Accessing or modifying the field of a null object.
  • Taking the length of null as if it were an array.
  • Accessing or modifying the slots of null as if it were an array.
  • Throwing null as if it were a Throwable value.

Applications should throw instances of this class to indicate other illegal uses of the null object.

It is also the case that if you attempt to use a null reference with synchronized, that will also throw this exception, per the JLS:

SynchronizedStatement:
    synchronized ( Expression ) Block
  • Otherwise, if the value of the Expression is null, a NullPointerException is thrown.

How do I fix it?

So you have a NullPointerException. How do you fix it? Let's take a simple example which throws a NullPointerException:

public class Printer {
    private String name;

    public void setName(String name) {
        this.name = name;
    }

    public void print() {
        printString(name);
    }

    private void printString(String s) {
        System.out.println(s + " (" + s.length() + ")");
    }

    public static void main(String[] args) {
        Printer printer = new Printer();
        printer.print();
    }
}

Identify the null values

The first step is identifying exactly which values are causing the exception. For this, we need to do some debugging. It's important to learn to read a stacktrace. This will show you where the exception was thrown:

Exception in thread "main" java.lang.NullPointerException
    at Printer.printString(Printer.java:13)
    at Printer.print(Printer.java:9)
    at Printer.main(Printer.java:19)

Here, we see that the exception is thrown on line 13 (in the printString method). Look at the line and check which values are null by adding logging statements or using a debugger. We find out that s is null, and calling the length method on it throws the exception. We can see that the program stops throwing the exception when s.length() is removed from the method.

Trace where these values come from

Next check where this value comes from. By following the callers of the method, we see that s is passed in with printString(name) in the print() method, and this.name is null.

Trace where these values should be set

Where is this.name set? In the setName(String) method. With some more debugging, we can see that this method isn't called at all. If the method was called, make sure to check the order that these methods are called, and the set method isn't called after the print method.

This is enough to give us a solution: add a call to printer.setName() before calling printer.print().

Other fixes

The variable can have a default value (and setName can prevent it being set to null):

private String name = "";

Either the print or printString method can check for null, for example:

printString((name == null) ? "" : name);

Or you can design the class so that name always has a non-null value:

public class Printer {
    private final String name;

    public Printer(String name) {
        this.name = Objects.requireNonNull(name);
    }

    public void print() {
        printString(name);
    }

    private void printString(String s) {
        System.out.println(s + " (" + s.length() + ")");
    }

    public static void main(String[] args) {
        Printer printer = new Printer("123");
        printer.print();
    }
}

See also:

I still can't find the problem

If you tried to debug the problem and still don't have a solution, you can post a question for more help, but make sure to include what you've tried so far. At a minimum, include the stacktrace in the question, and mark the important line numbers in the code. Also, try simplifying the code first (see SSCCE).

@Dennis Meng 2014-06-08 01:30:10

+1 Good to have an example that includes going through the stacktrace; it's important to show why reading it is important for debugging NPE. (and why we almost always look for a stacktrace when someone posts a question about an error)

@Ruchir Baronia 2015-12-10 07:07:51

You mentioned debugging...How does that work? I have been researching the topic for a while now, but can find nothing. I'm sure an amazing teacher like you can teach it to me in a second! Thanks so much! :-)

@fgb 2015-12-10 10:22:30

@RuchirBaronia A debugger allows you to step through a program line by line to see which methods are called and how variables are changed. IDEs should have some tools to do this. See vogella.com/tutorials/EclipseDebugging/article.html for example.

@fgb 2015-12-10 11:33:09

@RuchirBaronia You set breakpoints on the methods around any NullPointerExceptions as seen in the stacktrace, and check the values of variables against what you expect them to be. If you know a variable is null when it shouldn't be, then you can set breakpoints around any code that changes the value. There are also conditional breakpoints you can use which will tell you when a value changes.

@Tiny 2016-02-27 02:05:29

Setting String objects to an empty string as their default value is considered to be a poor practice.

@Massimo 2017-06-30 12:32:48

i suggest also static analysis tools, like FINDBUGS en.m.wikipedia.org/wiki/FindBugs

@Cafebabe 2018-10-04 22:48:30

Using NonNull annotations can help catch it.

@Makoto 2014-05-25 06:11:58

Another occurrence of a NullPointerException occurs when one declares an object array, then immediately tries to dereference elements inside of it.

String[] phrases = new String[10];
String keyPhrase = "Bird";
for(String phrase : phrases) {
    System.out.println(phrase.equals(keyPhrase));
}

This particular NPE can be avoided if the comparison order is reversed; namely, use .equals on a guaranteed non-null object.

All elements inside of an array are initialized to their common initial value; for any type of object array, that means that all elements are null.

You must initialize the elements in the array before accessing or dereferencing them.

String[] phrases = new String[] {"The bird", "A bird", "My bird", "Bird"};
String keyPhrase = "Bird";
for(String phrase : phrases) {
    System.out.println(phrase.equals(keyPhrase));
}

@Shailendra Singh 2016-07-08 15:20:31

operation on uninitialized object at instance level(not the class level) will lead to NullPointerException. operation need to be instance specific. if operation is at class level, saying calling a static method on uninitialized object then it will not throw NullPointerException exception. Even primitive wrapper class objects throws NullPointerException.

@tomj0101 2017-12-04 05:49:00

1. NullPointerException is a RuntimeException, that means will appear when your program is running, you will not at compilation time.! :(, but most of the IDE help you to discover this. 2. Minimize the use of the keyword 'null' in assignment statements. :) Reference url:

@Makoto 2017-12-04 05:54:27

@tomj0101 I'm thoroughly unclear as to why you made that comment... But to your second point, a pattern before Optional was to return null. The keyword is fine. Knowing how to guard against it is critical. This offers one common occurrence of it and ways to mitigate it.

@Shomu 2018-05-29 10:14:14

NullPointerException is a run-time exception which is not recommended to catch it, but instead avoid it.

@Makoto 2018-05-29 13:25:12

@Shomu: At what point do I even suggest that it should be caught?

@L. G. 2014-06-25 11:17:08

A lot of explanations are already present to explain how it happens and how to fix it, but you should also follow best practices to avoid NullPointerException at all.

See also: A good list of best practices

I would add, very important, make a good use of the final modifier. Using the "final" modifier whenever applicable in Java

Summary:

  1. Use the final modifier to enforce good initialization.
  2. Avoid returning null in methods, for example returning empty collections when applicable.
  3. Use annotations @NotNull and @Nullable
  4. Fail fast and use asserts to avoid propagation of null objects through the whole application when they shouldn't be null.
  5. Use equals with a known object first: if("knownObject".equals(unknownObject)
  6. Prefer valueOf() over toString().
  7. Use null safe StringUtils methods StringUtils.isEmpty(null).

@Amaresh Pattanayak 2015-04-17 12:58:50

In j2ee projects,Nullpointer exception is very common.Some cases reference variables got null values.So You should check the variable initialization properly.And during conditional statement you should always check that flag or reference contains null or not like:- if(flag!=0) { ur code that uses flag }

@Jan Chimiak 2016-03-05 10:34:20

It is worth mentioning that some IDEs (e.g. Eclipse) offer automatic nullity analisys based on customizable annotations (e.g. @Nullable as listed above) and warn about potential errors. It is also possible to infer and generate such annotations (e.g. IntelliJ can do that) based on existing code structure.

@Lakmal Vithanage 2017-02-17 06:52:33

First thing should do is before using a nullable object, you should check whether is it null, using if (obj==null).If it is null then you should write code to handle that also.

@L. G. 2017-02-27 09:43:26

IMO, it is preferable to avoid returning null objects in methods when possible and use annotation when null input parameters are not allowed in order to, by contract, reduce the amount of ´if (obj==null)´ in the code and improve the code readability.

@Stephen C 2017-05-21 07:52:34

Read this ... before you accept these "best practices" as truth: satisfice.com/blog/archives/27

@Prasad Kamdi 2017-06-28 09:39:06

A NULL pointer is one that points to nowhere or null reference. When you dereference a pointer p, you say "give me the data at the location stored in "p". When p is a null pointer, the location stored in p is nowhere, you're saying "give me the data at the location 'nowhere'". Obviously it can't do this, so it throws a NULL pointer exception. In general, it's because something hasn't been initialized properly. public void doSomething(Object obj){ //check for null if(obj != null){ //do something } else { //do something else } }

@Roland 2017-11-10 10:43:18

I also use final on parameters as the instance (where it points to) should mostly (99.999% of all parameters) not be changed. Sure you can still change values.

@bvdb 2018-04-25 16:38:59

Marking a (temporary) fieldfinal means that you can't reassign it. How can this produce/avoid a NullPointerExceptions at all ? --> conclusion: it is completely off topic.

@MrZebra 2008-10-20 13:25:08

A NULL pointer is one that points to nowhere. When you dereference a pointer p, you say "give me the data at the location stored in "p". When p is a null pointer, the location stored in p is nowhere, you're saying "give me the data at the location 'nowhere'". Obviously, it can't do this, so it throws a NULL pointer exception.

In general, it's because something hasn't been initialized properly.

@bvdb 2018-04-25 16:40:09

Are we creating a database ? --> NULL is written as null in java. And it's a case sensitive thing.

@TheRealChx101 2018-09-08 22:45:48

Lol. @bvdb Chill.

@TheRealChx101 2018-09-08 22:46:41

"A NULL pointer is one that points to nowhere" I disagree. Null pointers don't point to nowhere, they point to null values.

@MrZebra 2018-09-10 07:43:43

@TheRealChx101 A null pointer and a pointer to a null value are different things - a null pointer does not point to a null value. Suppose you have a pointer to a pointer: pointer A points to pointer B, and pointer B is null. In this case, pointer A points to a null value, and pointer B is a null pointer.

@Bill the Lizard 2008-10-20 13:20:44

NullPointerExceptions are exceptions that occur when you try to use a reference that points to no location in memory (null) as though it were referencing an object. Calling a method on a null reference or trying to access a field of a null reference will trigger a NullPointerException. These are the most common, but other ways are listed on the NullPointerException javadoc page.

Probably the quickest example code I could come up with to illustrate a NullPointerException would be:

public class Example {

    public static void main(String[] args) {
        Object obj = null;
        obj.hashCode();
    }

}

On the first line inside main, I'm explicitly setting the Object reference obj equal to null. This means I have a reference, but it isn't pointing to any object. After that, I try to treat the reference as though it points to an object by calling a method on it. This results in a NullPointerException because there is no code to execute in the location that the reference is pointing.

(This is a technicality, but I think it bears mentioning: A reference that points to null isn't the same as a C pointer that points to an invalid memory location. A null pointer is literally not pointing anywhere, which is subtly different than pointing to a location that happens to be invalid.)

@mmr 2009-02-20 04:06:16

I understood everything you wrote there, but only because I've been coding for a while and know what a 'pointer' and a 'reference' are (and what null is, for that matter). When I try to dive right into explanations like that, my students look at me crosseyed, because there's not enough background.

@Bill the Lizard 2009-02-20 04:32:49

@mmr: Thanks for the feedback, you make a valid point. It's difficult on the internet to really judge where someone is at, and at what level it's safe to start an explanation. I'll try revising this again.

@Ilmari Karonen 2014-01-18 09:28:26

A more common way to get a NullPointerException in practice would be forgetting to explicitly initialize a member variable to something other than null before using it, like this. With local variables, the compiler would catch this error, but in this case it doesn't. Maybe that would make a useful addition to your answer?

@user207421 2015-06-13 02:31:25

References don't 'point to null'. They are null, or point to an object.

@Bill the Lizard 2015-06-13 03:06:30

@EJP "A null pointer is literally not pointing anywhere..."

@user207421 2015-08-11 02:01:09

Exactly.So it doesn't 'point to null'.

@Bill the Lizard 2015-08-11 10:59:25

@EJP Which is exactly what that paragraph is pointing out.

@Steve Powell 2016-07-06 22:42:48

@EJP I think your points are valid, so I've updated the answer to be clearer and to avoid saying 'points to null' where it did.

@Bill the Lizard 2016-07-06 23:07:14

@StevePowell I indicated a long time ago that I didn't want my answer to change. Please respect the intent of the original author.

@Steve Powell 2016-07-14 11:19:00

Sorry, I was "improving the answer" as requested in the top of this stackoverflow item (This question's answers are a collaborative effort: if you see something that can be improved, just edit the answer to improve it!) I disagree that your version is better, IMO @EJB has valid points; but you are quite welcome to keep your answer intact, confusing though it is.

@Nic Hartley 2017-02-20 01:49:57

I'm not sure if it's the same in Java, but in C, NULL is the pointer to memory location 0, which is defined by the standard as an invalid memory location (in the sense that you can't read/write the value there). So, if it's the same in Java, more accurate may be "pointing to a specific, predetermined invalid memory spot that means 'has no value'".

@Steve Powell 2017-03-23 15:40:29

@QPaysTaxes NULL in C is nearly always a macro for the literal zero (o). If interpreted as a pointer this points to the memory address zero, which is normally not addressable, and certainly not updatable. It is not the same in Java, where null is a keyword, and denotes a (typeless) value which is assignable to object variables or fields. It does not "point to null", it isn't a pointer at all.

@Mads Boyd-Madsen 2017-11-26 21:12:59

I find the example misleading. If hashCode() had been an extension method, the call could well have passed through. Better to show examples where you try to access a field.

@Bill the Lizard 2017-11-27 01:57:03

@MadsBoyd-Madsen This is Java code written in 2008. There's nothing misleading about it.

@Bill the Lizard 2017-11-27 12:09:23

@MadsBoyd-Madsen No worries. The year this was published isn't being displayed as it normally would, since it's a community wiki post that's been edited many times.

@javid piprani 2013-09-24 06:01:46

A null pointer exception is an indicator that you are using an object without initializing it.

For example, below is a student class which will use it in our code.

public class Student {

    private int id;

    public int getId() {
        return this.id;
    }

    public setId(int newId) {
        this.id = newId;
    }
}

The below code gives you a null pointer exception.

public class School {

    Student obj_Student;

    public School() {
        try {
            obj_Student.getId();
        }
        catch(Exception e) {
            System.out.println("Null Pointer ");
        }
    }
}

Because you are using Obj_Student, but you forgot to initialize it like in the correct code shown below:

public class School {

    Student obj_Student;

    public School() {
        try {
            obj_Student = new Student();
            obj_Student.setId(12);
            obj_Student.getId();
        }
        catch(Exception e) {
            System.out.println("Null Pointer ");
        }
    }
}

@Mysticial 2013-09-24 06:20:14

While this is a nice example, may I ask what it adds to the question that isn't already covered by all the other answers?

@Adrian Shum 2013-09-24 06:32:32

It is simply inappropriate to use the word "uninitialized" here. The example you shown is in fact "initialized", and it is initialized with null. For uninitialized variables, compiler will complain to you.

@Stephen C 2015-05-27 13:35:16

An NPE may be an indicator that you are using an uninitialized field. It may be an indicator that you are doing other things. Oversimplifying to a single cause like this does not help someone solve NPE problems ... if the actual cause is not this one.

@nathan1138 2013-04-17 02:57:16

A null pointer exception is thrown when an application attempts to use null in a case where an object is required. These include:

  1. Calling the instance method of a null object.
  2. Accessing or modifying the field of a null object.
  3. Taking the length of null as if it were an array.
  4. Accessing or modifying the slots of null as if it were an array.
  5. Throwing null as if it were a Throwable value.

Applications should throw instances of this class to indicate other illegal uses of the null object.

Reference: http://docs.oracle.com/javase/8/docs/api/java/lang/NullPointerException.html

@Emiliano 2016-03-23 13:06:55

Keep it simple, I like this answer, add this if you consider correct - Access to uninitialized attribute of an object

@Stephen C 2016-05-19 06:57:05

@Emiliano - simply accessing an initialized attribute does not cause an NPE. It is what you >>do<< with the uninitialized attribute value that causes the NPE.

@Dominique Unruh 2016-09-18 17:07:12

This is from docs.oracle.com/javase/8/docs/api/java/lang/…. -1 for quoting without reference.

@Stephen C 2017-10-23 10:16:02

If you want more cases: 1) using a null as the target of a synchronized block, 2) using a null as the target of a switch, and unboxing null.

Related Questions

Sponsored Content

40 Answered Questions

[SOLVED] How do I convert a String to an int in Java?

22 Answered Questions

[SOLVED] What is a serialVersionUID and why should I use it?

46 Answered Questions

38 Answered Questions

[SOLVED] How do I efficiently iterate over each entry in a Java Map?

62 Answered Questions

[SOLVED] How do I generate random integers within a specific range in Java?

  • 2008-12-12 18:20:57
  • user42155
  • 3655218 View
  • 3087 Score
  • 62 Answer
  • Tags:   java random integer

14 Answered Questions

[SOLVED] What is a JavaBean exactly?

50 Answered Questions

[SOLVED] How do I fix android.os.NetworkOnMainThreadException?

21 Answered Questions

[SOLVED] What is reflection and why is it useful?

26 Answered Questions

1 Answered Questions

What is a MalformedURLException , and how do I fix it?

  • 2018-04-07 16:34:35
  • Dipanshu Mahla
  • 46 View
  • -1 Score
  • 1 Answer
  • Tags:   java exception

Sponsored Content