Thanks for the inputs. We hv traced this problem to a bug with Tomcat server. Basically the tomcat server is sending the response before the context/session is set. Since it is open source, we modified the code and that change has resolved this 500 error. The change we hv made is not the best possible solution and we are evaluating changes on the codes. (Changed jasper.jar JSPServletWrapper.java)
Can you analyze what would be code changes on application side in this case? On Sat, Jul 4, 2009 at 2:52 PM, Pid <p...@pidster.com> wrote: > On 4/7/09 00:22, Konstantin Kolinko wrote: > >> HttpSession session = request.getSession(); >>> >> >> Is the request a legit one (that is, the one that is being served by >> Tomcat now)? >> >> Requests are recycled immediately after their processing is done, >> and it can result in null being returned by that method (though throwing >> an IllegalStateException would be better). >> > > (See partial stacktrace below.) > > The Settings object looks like it is the source of the NullPointerException > and it looks like it is being statically initialised. > > I don't know what that object is, so I asked for more info - the OP is yet > to respond, unless I missed that message? > > How it is being initialised, it seems to me, is the source of the problem. > Does the initialisation depend on an HttpSession object or on some other > parameters? > > p > > > > > > > *root cause* >>>>> >>>>> java.lang.NullPointerException >>>>> com.teradata.x2.context.Settings.getSettings(Settings.java:102) >>>>> >>>>> >>>>> >>>>> com.teradata.x2.context.ServletProcessContext.getSettings(ServletProcessContext.java:38) >>>>> >>>>> It's probably not that random. >>>> >>>> What is at Settings.java, line 102? >>>> >>>> p >>>> >>> > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- Regards, Achal Patel.
