pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Status DISCARD ALL 2+ messages / 2 participants [nested] [flat]
* Status DISCARD ALL @ 2016-02-19 02:39 ALEXANDER JOSE <aangelj@hotmail.com> 2016-02-19 03:16 ` Re: [pgsql-es-ayuda] Status DISCARD ALL Horacio Miranda <hmiranda@gmail.com> 0 siblings, 1 reply; 2+ messages in thread From: ALEXANDER JOSE @ 2016-02-19 02:39 UTC (permalink / raw) To: pgsql-admin; Postgres Español <pgsql-es-ayuda@postgresql.org> Our platform consists of two servers with database postgresql v9.3, v3.3 pgpool for high availability on debian OS v7, and we have many connections webserver servers. The problem is presented when down two servers in weblogic that are clustered, and the pgpool connection status discard all remain, making it impossible to back up both servers WebLogic, to solve it we must lower the pgpool of each nodes so that sessions that were to discard all canceled status and weblogic can start and open connections without error. We would like to know if there are any configuration parameter that can kill pgpool sessions remaining discard all status. Alexander Angel DAB Postgresql Venezuela = ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: [pgsql-es-ayuda] Status DISCARD ALL 2016-02-19 02:39 Status DISCARD ALL ALEXANDER JOSE <aangelj@hotmail.com> @ 2016-02-19 03:16 ` Horacio Miranda <hmiranda@gmail.com> 0 siblings, 0 replies; 2+ messages in thread From: Horacio Miranda @ 2016-02-19 03:16 UTC (permalink / raw) To: ALEXANDER JOSE <aangelj@hotmail.com>; pgsql-admin; Postgres Español <pgsql-es-ayuda@postgresql.org> Sabes, este es un Foro en español y eres de Venezuela, por que nos escribes en Ingles ? On 2/19/2016 3:39 PM, ALEXANDER JOSE wrote: > Our platform consists of two servers with database postgresql v9.3, v3.3 > pgpool for high availability on debian OS v7, and we have many > connections webserver servers. The problem is presented when down two > servers in weblogic that are clustered, and the pgpool connection status > discard all remain, making it impossible to back up both servers > WebLogic, to solve it we must lower the pgpool of each nodes so that > sessions that were to discard all canceled status and weblogic can start > and open connections without error. > > We would like to know if there are any configuration parameter that can > kill pgpool sessions remaining discard all status. > > If your problem is Zombie process, the only way is performing "kill -9" Perhaps, the following link may help. http://stackoverflow.com/questions/13236160/is-there-a-timeout-for-idle-postgresql-connections http://www.pgpool.net/mantisbt/view.php?id=45 BTW, what Weblogic documentation say about postgresql-pgpool-WebLogic ? > > Alexander Angel > DAB Postgresql > Venezuela -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2016-02-19 03:16 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2016-02-19 02:39 Status DISCARD ALL ALEXANDER JOSE <aangelj@hotmail.com> 2016-02-19 03:16 ` Horacio Miranda <hmiranda@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox