Jo Desmet wrote:"So it comes to going deeper into the stacktrace until you stumble upponcode that is actually writen by yourself."If I understand you correctly Jo, what you've just said is that the firsttwo lines of my error code are "prepackaged Java methods" (Therefore implyingthat the problem isn't in that code). The next error message, on the otherhand, is the first error message that is not a "prepackaged Java method"(my own code) so therefore the problem must reside there. That is how Tomfound the problem right away.Jo, before I try your next suggestion regarding the JIT compiler, if Iturn it off using "-Djava.compiler=NONE", how do I turn it back on! I don'twant to get stranded! Or, since I'm compiling in DOS is "On" the defaultand to turn it off I have to type "-Djava.compiler=NONE" each time I wantto turn it off. Pardon my cautions here, but I have enough variables totry to keep track of here while I'm learning Java - one less headache meansa lot.Thanks ALOT to all those who read and help us newbies out!)))))))Mark"Jo Desmet" <[email protected]> wrote:>You are indeed looking at a stack trace. The top line is where the actual>fatal action appeared: passing a null as a parameter is by itself not>illegal, but calling a method from a null object is fatal. So it comes to>going deeper into the stacktrace until you stumble uppon code that is>actually writen by yourself.>Sometimes in stead of the line number, you will see "Compiled Code" thatis>because the JVM has invoked its JIT compiler on this part of your codingand>thus has lost any tracing information. It could be usefull in the debugging>process to turn of your JIT compiler by adding the following option to your>java command: "-Djava.compiler=NONE".>>greetings, Jo.>>"Mark Sorteberg" <[email protected]> wrote in message>news:[email protected]...>>>> Thanks Tom:>>>> I just didn't know how to read the error code. What clued you in to line>> 217 as the problem area. I assumed it was 377 or maybe 458. I made the>> false assumption, based on past debugging experience - solve the top item>> in the list first. I guess this gets down to a more basic question asto>> how to read Java error code. I assume we have some sort of a stack trace>> here.>>>> What does the bottom error message mean? Now that I fixed this problem>when>> I run the code I get four errors all with "Compiled Code" at the end of>each>> line. Thanks again for your help.>>>> Any good pointers or resources on how to read error code?>>>> Being the only developer has its drawbacks,>>>> Mark>>>> "Tom Duffy" <[email protected]> wrote:>> >>> >Hello Mark:>> >>> >It looks like you are passing a null String into parseInt(). You're>getting>> >a NumberFormatException as a result. The error looks to be at line 217>> of>> >GenerateReports.java. I'd check there and make sure I'm not passingin>> something>> >that won't parse to an int.>> >>> >HTH,>> >>> >Tom Duffy>> >>> >"Mark Sorteberg" <[email protected]> wrote:>> >>>> >>My Java code compiles fine, but when I go to run it I get this message:>> >>>> >>Exception in thread "main" java.lang.NumberFormat Exception: null>> >> at java.lang.Integer.parseInt(Integer.java:377)>> >> at java.lang.Integer.parseInt(Integer.java:458)>> >> at GenerateReports.<init>(GenerateReports.java:217)>> >> at GenerateReports.main(GenerateReports.java, Compiled Code)>> >>>> >>Any help would be appreciated.>> >>>>>