Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
From: "eurotrans-Verlag" <verlag.preisser@t-online.de>
To: "'Tomcat Users List'" <users@tomcat.apache.org>
References: <004b01cc3c3d$43795b00$ca6c1100$@preisser@t-online.de>
 <4E16053C.4000000@christopherschultz.net>
 <000301cc3ce0$6d9c4340$48d4c9c0$@preisser@t-online.de>
 <4E167EC9.9070007@christopherschultz.net>
In-Reply-To: <4E167EC9.9070007@christopherschultz.net>
Subject: RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16
Date: Fri, 8 Jul 2011 14:00:19 +0200
Message-ID: <002501cc3d66$9bfc3f20$d3f4bd60$@preisser@t-online.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: Acw9InGK3KZzmXqQQCmj4fHgDWobdAAQkllw
Content-Language: de

Hi Christopher,

>=20
> 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 str =3D null;
System.out.println(
        "blah" +
        str.toLowerCase()
        );

(note that the str.toLowerCase() which will throw a NPE is two lines =
below the System.out.println() call).
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 the compiled =
Tomcat, thus I supposed that only container or the logger could be =
null).


>=20
> Problem solved?
>=20

Well, I don't know what the original problem was, so I don't know if it =
is solved. ;)
My concern at the moment is not the original exception that occurred, =
but the NPE that suppressed that exception, because if it happens again, =
I will not able to see what was the original exception.

As Pid said, it could have something to do with the old context which =
was still waiting for a request to finish, and as I stated in the other =
message, I could reproduce a NPE, but in StandardContextValve.invoke() =
(there "context" was null). But NPEs thrown are never good, are they?


Regards,

Konstantin Prei=C3=9Fer


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org