| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Poul Møller Hansen <freebsd(at)pbnet(dot)dk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Loosing connection with the database |
| Date: | 2005-04-02 17:00:07 |
| Message-ID: | 4544.1112461207@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?UTF-8?B?UG91bCBNw7hsbGVyIEhhbnNlbg==?= <freebsd(at)pbnet(dot)dk> writes:
> I'm experiencing some strange problems with a Java application which I
> have made.
> Suddently it looses connection with the database, and in the server log
> i can find:
> 2005-04-02 00:09:01 ERROR: invalid string enlargement request size
> 1358954492
> 2005-04-02 00:09:01 WARNING: AbortTransaction and not in in-progress
> state
> 2005-04-02 00:09:01 FATAL: invalid frontend message type 82
This indicates the client code didn't follow the protocol properly,
ie, it sent garbage where a message length word ought to be.
This sort of thing has been seen to occur when multiple client-side
threads try to use the same database connection without proper locking
to ensure only one thread uses it at a time. See for example
http://archives.postgresql.org/pgsql-hackers/2004-09/msg00104.php
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Poul Møller Hansen | 2005-04-02 17:28:54 | Re: Loosing connection with the database |
| Previous Message | Peter Eisentraut | 2005-04-02 16:57:34 | Re: [GENERAL] plPHP in core? |