Message-ID: <027101bdbff2$e9e0b310$8355e5ce@tesla.base2inc.com>
Reply-To: "Frank Morton" <fmorton@mail.base2inc.com>
From: "Frank Morton" <fmorton@mail.base2inc.com>
To: "pgsql-interfaces MailingList" <pgsql-interfaces@postgresql.org>
Subject: JDBC IOException: Broken pipe
Date: Tue, 4 Aug 1998 16:57:46 -0500

I'm new to the list, though I have been using postgresql for awhile.

My understanding is that the JDBC driver is not thread safe, so
what I have been doing is opening a new connection to the database
for each thread. In this application, generally 5 to 10 threads
are running.

I am using Solaris 2.5.1 with postgresql 6.3.2.

My problem is that after running "awhile" (which I will call 24 hours,
though I am not sure yet if that is long or short) even the most
simple application will start getting java.io.IOException: Broken pipe
exceptions, which I assume means that the database has disappeared.
Is that right?

I am looking for advice in general regarding how I am handling
the threading situation and if anyone can shed any light on how
to avoid "Broken pipe".

Thanks.


_________________________________
Frank Morton (fmorton@mail.base2inc.com)
Voice: (317) 876-3355
FAX: (317) 876-3398
Home: (317) 574-0815