RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-08 Thread eurotrans-Verlag
Hi Christopher, My experience with the Sun/Oracle compiler is that lines 288 and 289 will never be indicated in a stack trace: the line number of the start of the statement is considered the line number for the entire statement. Well, I made a small test program with this code: String

Re: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-08 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Konstantin, On 7/8/2011 8:00 AM, eurotrans-Verlag wrote: After compiling and running it with the Oracle Java 1.6.0_26, the line number printed was the line with the str.toLowerCase(), not the System.out.println. So I assume the same is true for

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-08 Thread eurotrans-Verlag
Hi Christopher, The compiler must have gotten smarter than the last time I checked. I'm sorry: I compiled that code with the Eclipse compiler. When compiling it with the Oracle Java compiler (javac), it prints out the line number of the System.out.println. Maybe if Tomcat was compiled

Re: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-08 Thread Mark Thomas
On 08/07/2011 22:25, eurotrans-Verlag wrote: Hi Christopher, The compiler must have gotten smarter than the last time I checked. I'm sorry: I compiled that code with the Eclipse compiler. When compiling it with the Oracle Java compiler (javac), it prints out the line number of the

Re: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread Pid
On 07/07/2011 01:31, eurotrans-Verlag wrote: Hi all, I’m using Tomcat 7.0.16 on a system with Java 1.6.0_26 on Windows Serer 2008 and wondered about a strange NPE I got shortly after deploying a webapp to Tomcat: SCHWERWIEGEND: An exception or error occurred in the container during the

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread eurotrans-Verlag
Hi Pid, -Original Message- From: Pid [mailto:p...@pidster.com] Sent: Thursday, July 07, 2011 6:19 PM What is the request for and is the config of your Tomcat instance modified from the original download - if so, what has changed (config etc)? p I don't know which request

Re: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Konstantin, On 7/6/2011 8:31 PM, eurotrans-Verlag wrote: I’m using Tomcat 7.0.16 on a system with Java 1.6.0_26 on Windows Serer 2008 and wondered about a strange NPE I got shortly after deploying a webapp to Tomcat: SCHWERWIEGEND: An exception

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread eurotrans-Verlag
Hi Christopher, -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Thursday, July 07, 2011 9:13 PM Looks like it. I would be very interested to know which of those objects is null: the container, the logger, the wrapper, or the context. -

Re: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread Pid
On 07/07/2011 20:59, eurotrans-Verlag wrote: Hi Christopher, -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Thursday, July 07, 2011 9:13 PM Looks like it. I would be very interested to know which of those objects is null: the container,

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread eurotrans-Verlag
Hi Pid, -Original Message- From: Pid [mailto:p...@pidster.com] Sent: Thursday, July 07, 2011 10:24 PM Are you using parallel deployment or are you replacing the existing application when it's redeployed. Maybe the old context is the one throwing the error. p I don't use

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread eurotrans-Verlag
Maybe I can reproduce the NPE if I make a servlet that takes a long time to finish the request, to see what was the original exception that has been suppressed by the NPE. OK, I was able to reproduce a NPE in TC 7.0.16 with a Servlet that calls Thread.sleep(2), then make a request to

Re: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Konstantin, On 7/7/2011 3:59 PM, eurotrans-Verlag wrote: Hi Christopher, -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Thursday, July 07, 2011 9:13 PM Looks like it. I would be very

Re: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Konstantin, On 7/7/2011 5:45 PM, eurotrans-Verlag wrote: The logs on redeploy were this: 07.07.2011 00:24:09 org.apache.catalina.startup.HostConfig checkResources INFO: Undeploying context [] Uhh... that can't be good. Why does the context have

Re: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread Konstantin Kolinko
2011/7/8 Christopher Schultz ch...@christopherschultz.net: On 7/7/2011 5:45 PM, eurotrans-Verlag wrote: The logs on redeploy were this: 07.07.2011 00:24:09 org.apache.catalina.startup.HostConfig checkResources INFO: Undeploying context [] Uhh... that can't be good. Why does the context have

NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-06 Thread eurotrans-Verlag
Hi all, I’m using Tomcat 7.0.16 on a system with Java 1.6.0_26 on Windows Serer 2008 and wondered about a strange NPE I got shortly after deploying a webapp to Tomcat: SCHWERWIEGEND: An exception or error occurred in the container during the request processing java.lang.NullPointerException