From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Poul Møller Hansen <freebsd(at)pbnet(dot)dk> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Loosing connection with the database |
Date: | 2005-04-12 13:03:59 |
Message-ID: | Pine.BSO.4.56.0504120612001.20062@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 12 Apr 2005, [UTF-8] Poul Mller Hansen wrote:
> I have rewritten the application so every client thread is opening a new
> database connection, and yesterday it happened again.
> ---
> 2005-04-11 12:27:54 ERROR: invalid string enlargement request size
> 1358954492
> 2005-04-11 12:27:54 WARNING: AbortTransaction and not in in-progress
> state
> 2005-04-11 12:27:54 FATAL: invalid frontend message type
> 78
> ---
> The application is opening a socket listener, and every client
> connection opens a new connection to the database.
> The clients sends a status message every 2nd minute that are written to
> the database.
> I'm using Postgresql version 7.4.7 and jdbc driver version
> pg74.215.jdbc3.jar.
>
> Do you have a clue on what's going on ?
>
No, I don't. Do you have any more information? What is your code doing
when it fails? Just issuing a regular query? Are you using any of the
less common driver features: Large objects, fastpath api, a COPY patch?
If the driver had a protocol problem I would expect it to be rather
repeatable. If the driver had a synchronization problem it should have
disappeared when you moved to a single thread model. I've attached the
test script I've used to try and beat on the driver.
Kris Jurka
Attachment | Content-Type | Size |
---|---|---|
Threads.java | text/plain | 3.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2005-04-12 13:15:52 | Re: PostgreSQL 8.0.2 Now Available |
Previous Message | Patrick.FICHE | 2005-04-12 12:57:48 | Get Number of milliseconds for an intervall |