This content has been marked as final. Show 4 replies
Somewhere in your code you are using a variable or object
without initialising it. That's why you are getting the
Nullpointer Exception: you are trying to use something that does
not exist at that time.
The reason your program compiles perfectly is very simple: a
compiler only checks the syntax of your program, never what it
is supposed to do. Because of this, a Nullpointer exception will
not be noticed by the compiler.
Try looking over your code again, and look for objects that are
not initialised. Try to set some breakpoints or comment out
blocks that are safe, you'll find the error somewhere.
Best of luck,
we encountered the same error on aix4.3.3. in fact the error comes from a variable, that has not been initialized, jserv error log says the following:
[07/11/2001 10:00:54:098 GMT+00:00] esvportal/init
[07/11/2001 10:01:08:668 GMT+00:00] esvportal/Response status: 500 : java.lang.NullPointerException
i habe a public page with 4 jsp portlets and one pl/sql portlet. the plsql ist working, every one of the jsp portlets gets the "getAcceptLanguage" error
I had the exact same problem for a while.
I found I got the error when using the Opera browser. Using Netscape or Explorer did not cause the problem.
I expect my browser was not communicating language to the portlet properly.
I hope this helps. Hopefully the portlet authors will add a "catch" statement in the next release.
A lot of times you will get the NullPointerException because the classes it saw during compilation, it cannot find when it tries to contact the Adapter (the URL you call to get the testpage).
If you compile it in JDeveloper or other tools/utilities, a lot of times it places additional classes in the code outisde of standard Java/Servlet and PDK-Java classes. Make sure that you include these in your classpath for JServ as well.