From: | Markus Schaber <schabios(at)logi-track(dot)com> |
---|---|
To: | Sergei Georgiev <sergei(dot)georgiev(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Socket timeouts (probably) |
Date: | 2005-02-23 15:54:07 |
Message-ID: | 421CA71F.405@logi-track.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi, Sergej,
Sergei Georgiev schrieb:
> I have a really strange problem here. I've got two Fedora 2 machines -
> one for the database and one for a Java application to be run. When a
> transaction from the application is run against the database and the
> network cable is unplugged (or the machine is shut down) the database
> continues to hold the lock on the tables, which are used in the
> transaction. The lock is released in about 10-12 minutes, which in my
> case is not acceptable, because if another client starts a transaction
> against these locked tables his UI ties his hands until the lock on
> the tables is released and the transaction is complete.
> I started a 'netstat -atp' on the database machine and it turned out
> that the connection with the unplugged machine is still active (5
> connections actually, because of the connection pooling). So I assumed
> that the sockets are just hanging there until they timeout and then
> the locks are released.
Maybe you can set the TCP connection keepalive probing on the server to
about 30 seconds or so via /proc/sys/net. But this is only advisable if
your server does not serve any other purposes.
Markus
--
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios(at)logi-track(dot)com | www.logi-track.com
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Cottenceau | 2005-02-23 16:24:56 | PGStatement#setUseServerPrepare breaking PreparedStatement#executeUpdate return value? |
Previous Message | Sergei Georgiev | 2005-02-23 15:15:44 | Socket timeouts (probably) |