RE: Postgresql 7.0 JDBC exceptions - broken connecti ons ?
От | Peter Mount |
---|---|
Тема | RE: Postgresql 7.0 JDBC exceptions - broken connecti ons ? |
Дата | |
Msg-id | 1B3D5E532D18D311861A00600865478CF1AE65@exchange1.nt.maidstone.gov.uk обсуждение исходный текст |
Ответы |
Re: Postgresql 7.0 JDBC exceptions - broken connections ?
|
Список | pgsql-interfaces |
As usual when replying from here, replies prefixed with PM: -- Peter Mount Enterprise Support Maidstone Borough Council Any views stated are my own, and not those of Maidstone Borough Council. -----Original Message----- From: Gunnar R|nning [mailto:gunnar@candleweb.no] Sent: Thursday, May 25, 2000 12:38 PM To: pgsql-interfaces@postgresql.org Subject: [INTERFACES] Postgresql 7.0 JDBC exceptions - broken connections ? Hello, As I told you in an former mail I'm trying to migrate an application to use PostgreSQL 7.0. The application now seems to be working pretty well and I have 5 users that have been testing our web application with the PostgreSQL database for the past 24 hours. The application runs with a connection pool, but after some time some of these connections seems to be broken. Ie. only some of the queries work - I will change the connection pool code to handle this, but I would like to know if anybody know why the connections gets into an unusable state. Could it be back crashes or similar things ? I'm turning on debugging for the database server to see if can find anything there, but anyway here is the exception I get : PM: How long is it before the problem starts? I'm wondering if the problem is because the backend is sitting there for a long period. select distinct entity.*,location.loc_id,location.loc_name from entity,locationmap,location,entityindex2 as e0 where locationmap.ent_id=entity.ent_id and locationmap.loc_id=location.loc_id and e0.ei_word='kjøttbørsen' and e0.ent_id=entity.ent_id and ENT_STATUS=4 order by ent_title,location.loc_name,location.loc_id Unknown Response Type u PM: Does anyone [on Hackers] know what the u code is for? The fact it's in lower case tells me that the protocol/connection got broken somehow.
В списке pgsql-interfaces по дате отправления: