I experienced a similar problem some time ago that actually was related to
the Java end- Unfortunately I can't remember the exact message, but it might
be worth checking out-
Tomcat attempts to reload all of the affected classes if you recompile a
class that is part of a currently loaded context. In V3.2 they still didn't
have this process working very well, & so compiling a seemingly unrelated
class would cause the class that our Connection lives in to get reloaded,
thus invalidating all of the Connection instances.
This would of course only occur in a situation where you were doing
development work on the server in question.
-Nick
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org]On Behalf Of Tom Lane
> Sent: Tuesday, January 08, 2002 5:38 PM
> To: bcarterette@mail.liberty.k12.mo.us
> Cc: pgsql-jdbc@postgresql.org
> Subject: Re: [JDBC] The backend has broken the connection...
>
>
> bcarterette@mail.liberty.k12.mo.us writes:
> > I am running several databases on a PostgresQL server and webapps to go
> > with them on another server. For the past couple of days,
> several times
> > a day I've been getting a "The backend has broken the connection.
> > Possibly the action you have attempted has caused it to close." error.
> > When this happens, all connections close and anyone in the middle of a
> > session is screwed.
>
> Sounds like you are seeing backend crashes. Does the postmaster log
> show any complaints about unexpected child process exits? Are there
> any core files laying about in the database subdirectories? Ideally
> I'd like to see a debugger backtrace from a core file ...
>
> In any case, this is not a Java or JDBC problem, it's a backend problem.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>