Skip site navigation (1) Skip section navigation (2)

Re: JDBC driver

From: "Nick Fankhauser" <nickf(at)ontko(dot)com>
To: "Jacob Vennervald Madsen" <jvm(at)gopinocchio(dot)com>, <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: JDBC driver
Date: 2001-11-09 11:23:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc

We've had similar messages using Tomcat & JDBC. Although we haven't tracked
it down completely, it seems that something happens which caused Tomcat to
reload one or more classes, and in the process your connection to JDBC is
lost (assuming you have an open connection or pool of connections at the
time.) If you are using a pool and want to avoid reloading Tomcat when this
happens, you can use the Tomcat "Admin" tool to reload the context, which
will init the servlets.

Hope this helps.


Nick Fankhauser  nickf(at)ontko(dot)com  Phone 1.765.935.4283  Fax 1.765.962.9788
Ray Ontko & Co.     Software Consulting Services

> 2001-11-08 14:23:04,607 ERROR UserDBHandler  - Problem executing query
> 2001-11-08 14:23:04,607 ERROR UserDBHandler  - An I/O error has occured
> while flushing the output - Exception: Broken pipe
> Stack Trace:

In response to

  • JDBC driver at 2001-11-08 14:03:57 from Jacob Vennervald Madsen

pgsql-jdbc by date

Next:From: Nick FankhauserDate: 2001-11-09 11:28:27
Subject: Re: JDBC Connection
Previous:From: Nick FankhauserDate: 2001-11-09 11:18:18
Subject: Re: no suitable driver

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group