| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Stephen Davies <sdavies(at)sdc(dot)com(dot)au> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: JDBC issue |
| Date: | 2026-07-12 07:13:36 |
| Message-ID: | ED24FEAA-D867-4585-93EE-13AE67F4AE95@thebuild.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Jul 12, 2026, at 00:01, Stephen Davies <sdavies(at)sdc(dot)com(dot)au> wrote:
>
> I have several JDBC-based programs on my Rocky Linux 9.8 box.
> Postgresql 17.10 and JDBC 42.7.2.
> As of today, these programs all fail because the JDBC connections do not work and the following code example produces no output except:
>
> "org.apache.jasper.JasperException: An exception occurred processing [/jsp/browsewineries.jsp] at line [48] st1 is null".
Look at catalina.out (or journalctl -u tomcat) for the e.printStackTrace() output; that should get you the real exception. You can also check the PostgreSQL logs to see if it even made it to opening the connection.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Davies | 2026-07-12 07:40:59 | Re: JDBC issue |
| Previous Message | Stephen Davies | 2026-07-12 07:01:12 | JDBC issue |