Return-Path: 
 <tomcat-user-return-22947-qmlist-jakarta-archive-tomcat-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org
Received: (qmail 22454 invoked from network); 17 Jun 2002 19:23:24 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 17 Jun 2002 19:23:24 -0000
Received: (qmail 16350 invoked by uid 97); 17 Jun 2002 19:23:15 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org
Received: (qmail 16333 invoked by uid 97); 17 Jun 2002 19:23:14 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 16306 invoked by uid 98); 17 Jun 2002 19:23:14 -0000
X-Antivirus: nagoya (v4198 created Apr 24 2002)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Tomcat 4.1.3 ServletException
Date: Mon, 17 Jun 2002 15:21:58 -0400
Message-ID: <EAF2427CBCBD2641B56C8423BC18585B3F691D@US-VS1.corp.mpi.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Tomcat 4.1.3 ServletException
Thread-Index: AcIWMnzTJAEkYR0mQsGhC/eNny1E2QAAG8YA
From: "Shapira, Yoav" <Yoav.Shapira@mpi.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Howdy,
First of all, go have a cold coke or something ;)  Debugging while
frustrated is, well, frustrating ;) =20

>javax.servlet.ServletException: No results were returned by the query.
>at org.apache.jasper.runtime.PageContextImpl.handlePageException
>(PageContextImpl.java:479)
>at org.apache.jsp.main$jsp._jspService(Unknown Source)
><snip exception stack>
>
>There is a database query that is being executed in one of the
supporting
>beans for the page.  However, I have no IDEA what bean its occuring in
or
>which query is being executed.

If you wrote the supporting bean, can you perhaps output logging
information before trying to execute the query? =20

>Why doesn't Jasper tell me what line number and what bean its occuring
in?

Jasper probably doesn't tell you the line number because the bean was
not compiled with debugging information, which is usually required in
order to get line numbers in exception traces.

As to which bean is causing the exception, my guess is Jasper can't tell
you that because the bean didn't expect and thus doesn't catch this
exception.  ServletException is what the container is supposed to throw
when an exception propagates up, uncaught by any of your classes.

>Heck, I'd even settle at looking at the generated servlet .java file
and
>trying to find it myself, but it doesn't even list where the error
occured
>in the _jspService method in the sourcecode.

Would it be possible for you to attach a profiler/debugger, e.g.
OptimizeIt, to the running server?  Alternatively, can you write a
command-line program to test your compiled JSP class with dummy
requests?

Yoav


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>