Dear all,
I have a problem with a firewall which sits between my java web apps and
postgresql. That firewall kills idle postgresql connections each hour, so if
my web app is inactive for an hour, when the app tries to reconnect, it
receives an exception, because the jdbc application does not know
I have a problem with a firewall which sits between my java web apps and
postgresql. That firewall kills idle postgresql connections each hour, so if
my web app is inactive for an hour, when the app tries to reconnect, it
receives an exception, because the jdbc application does not know that
Thanks Tatsuo.
I originally started with that (num_init_children=16), but then when
all connections were used, even though they were idle, new connections
would hang forever. When I set client_idle_limit greater than 0, we
got errors like this:
PGError: ERROR: connection terminated due to client
Hello,
new problem :
2011-08-19 17:52:03 LOG: pid 8968: find_primary_node:
pgpool_walrecrunning does not exist
2011-08-19 18:01:25 LOG: pid 8990: pool_send_and_wait: Error or
notice message from backend: : DB node id: 1 backend pid: 10280
statement: message: cannot execute UPDATE in a
I originally started with that (num_init_children=16), but then when
all connections were used, even though they were idle, new connections
would hang forever.
Sure, it's normal behaviour for pgPool. The pooling is done in session
mode. It means that once a session is started, the pgpool
