Subject: Re: [pgsql-es-ayuda] Status DISCARD ALL
To: ALEXANDER JOSE <aangelj@hotmail.com>,
 postgres admin <pgsql-admin@postgresql.org>,
 =?UTF-8?Q?Postgres_Espa=c3=b1ol?= <pgsql-es-ayuda@postgresql.org>
References: <COL129-W8021542A62B62033C91C9FA5A00@phx.gbl>
From: Horacio Miranda <hmiranda@gmail.com>
Message-ID: <56C6890E.40803@gmail.com>
Date: Fri, 19 Feb 2016 16:16:30 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <COL129-W8021542A62B62033C91C9FA5A00@phx.gbl>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@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