Nullpointer Exception with BufferedWriter?

[Solarsonic]

I'm trying to write out a String array to a text file using a Buffered Writer.

It works fine when the array has 100 values but when I go higher than that it gives me a NullPointerException caused by the write() method.

This is my assignment code:

BufferedWriter writer = new BufferedWriter(new PrintWriter(file));

This is my enhanced for loop and closing code:

for(String s : usernames) {
writer.write(s);
writer.newLine();
	}
	writer.flush();
	writer.close();

I'm guessing this is because String[] arrays can't hold that much memory, if so what can I use to duplicate what I want?

Thanks a lot,
~Solarsonic

[Junky]

Not really sure from the info provided.

When you create an object array, it is filled with the default value of null. So if you create a String array with a length of 100 and fill 70 slots with Strings the other 30 slots will be null. If you then iterate over the full array and try and write all values out to the file then when it hits the 71st slot it will throw the NPE.

[Solarsonic]

Not really sure from the info provided.

When you create an object array, it is filled with the default value of null. So if you create a String array with a length of 100 and fill 70 slots with Strings the other 30 slots will be null. If you then iterate over the full array and try and write all values out to the file then when it hits the 71st slot it will throw the NPE.

Nope, that's not it. Checked it thoroughly just now for that.

What other possibilities are there? I'm familiar with the NullPointerException, I just can't seem to spot the problem for this. Is it possible that the writer is writing too much at once and too fast? Would the wait() method solve the problem?

[Junky]

The NPE message provides valuable information such as the stack trace. Each method that has been called is included as well as a line number. Go through the stack trace and find the first method that you wrote is listed. go to the line mentioned then look at evrything on that line that maybe null. On the previous line place a print statement to print out all the things that maybe null (if there are more than one then use several print statements. When you have determined exactly what is null then do a bit more detective work and see why it is null.

No it has nothing to do with memory or speed.