Re: resultset.first() untrappable error - Mailing list pgsql-jdbc

From kevin@mtel.co.uk (kevin)
Subject Re: resultset.first() untrappable error
Date
Msg-id 6675f17.0308190023.74c8eade@posting.google.com
Whole thread Raw
In response to Re: resultset.first() untrappable error  (kevin@mtel.co.uk (kevin))
List pgsql-jdbc
nickf@ontko.com ("Nick Fankhauser") wrote in message news:<NEBBLAAHGLEEPCGOBHDGEEHLIAAA.nickf@ontko.com>...
> Kevin-
>
> Looking at the code fragments, there's nothing obviously wrong, but we're
> just seeing pieces. Given that nothing is obvious, I'd suggest it is time to
> just start adding some debug statements to narrow it down...
>
> > a call has been made to the jsp page defined isErrorPage=true with no
> > valid
> > Exception object.
> > exception==null
>
> So apparently an exception is being thrown, but is invalid by the time it
> gets passed to the error page. Perhaps you can debug by catching the
> exception before it gets to the jsp and dumping the stack to System.out so
> you can see what's up in the tomcat stdout log. (Is this in a servlet or a
> jsp?)

i cant trap the exception. if i place the results.first() call in a
try {
}
catch (SQLExcception) {
}
catch (Exception) {
}
it still jumps straight to the error page
>
>
> > the code will jump straight to the error bypassing any code of the
> > form
> > if(rst.first()) {
> >    // do something
> > }
>
> I guess the first thing I'd do is something like:
>  if (rst == null) System.out.println("rst is null");
>  if(rst.first()) {
>     // do something
>  }
>
will try this. thanks for helping.

kev.

>
> -Nick
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

pgsql-jdbc by date:

Previous
From: kevin@mtel.co.uk (kevin)
Date:
Subject: Re: odd behaviour of prepared statement
Next
From: rajesh kumar
Date:
Subject: reg:"Driver Not found-error"- need u r suggestions