invalid string enlargment PG 7.4.5 ( SOLVED )

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't see the last post about the issue I had
and that was solved ( due I think to last days problems),
I post it here again:

================================================================

Tom Lane wrote:

| Gaetano Mendola <mendola(at)bigfoot(dot)com> writes:
|
|> ERROR: invalid string enlargement request size 1476395004
|> DEBUG: AbortCurrentTransaction
|> WARNING: AbortTransaction and not in in-progress state
|> ERROR: could not send data to client: Broken pipe
|> PANIC: error during error recovery, giving up
|
|
|
|> do you have any idea on what could be the reason ?
|
|
|
| I'm betting on a communications failure. What I see there is a few
| bytes of corrupted data received from the client (ie, a ridiculous
| message-length word) followed by abrupt disconnect *by the client*.
|
| You have any logs indicating what might have happened at the client
| end?

After further investigation, I discover a Servlet ( that was there running
since six months ) that was not implementing the SingleThreadModel.

Basically more instances of the same servlet were using the same
DB connection without be aware of the others. This was causing the second
servlet performing a query on an already closed communication with the server!

The question are:

~ - why with the 7.4.2 I never notice it ( I know a critical race could be
~ there for years and pop-ut in any moment ) ?

~ - why for a not well client behaviour the server go in PANIC ?

Regards
Gaetano Mendola
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBOk4p7UpzwH2SGd4RAogLAKD94bNTV5PPfhKcxvdCKBolObzFJgCg8bSL
LqQS9b1H8grYNBcGKxErc28=
=n1S4
-----END PGP SIGNATURE-----