Re: BUG #5829: No buffer Space Available(maximum connection reached?) from postgres edb driver

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: BUG #5829: No buffer Space Available(maximum connection reached?) from postgres edb driver
Дата
Msg-id 4D2FEBDB.3030509@postnewspapers.com.au
обсуждение исходный текст
Ответ на BUG #5829: No buffer Space Available(maximum connection reached?) from postgres edb driver  ("Listening Platform" <listening.platform@gmail.com>)
Список pgsql-bugs
On 01/11/2011 05:41 PM, Listening Platform wrote:
>
> The following bug has been logged online:
>
> Bug reference:      5829
> Logged by:          Listening Platform
> Email address:      listening.platform@gmail.com
> PostgreSQL version: 8.4 AS
> Operating system:   Windows 2003 server SP2
> Description:        No buffer Space Available(maximum connection reached?)
> from postgres edb driver


> Caused by: java.net.SocketException: No buffer space available (maximum
> connections reached?): connect
>     at java.net.PlainSocketImpl.socketConnect(Native Method)
>     at java.net.PlainSocketImpl.doConnect(Unknown Source)
>     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
>     at java.net.PlainSocketImpl.connect(Unknown Source)
>     at java.net.SocksSocketImpl.connect(Unknown Source)
>     at java.net.Socket.connect(Unknown Source)
>     at java.net.Socket.connect(Unknown Source)
>     at java.net.Socket.<init>(Unknown Source)
>     at java.net.Socket.<init>(Unknown Source)
>     at com.edb.core.PGStream.<init>(PGStream.java:70)
>     at
> com.edb.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryIm
> pl.java:115)
>     ... 20 more

It'd be nice to have those "20 more". Java's habit of truncating
exception stack traces is one of the more annoying things it does.

In this case, though, it seems pretty likely that you

> When the error occured we were not able to connect to internet and DB

Hang on ... you mean that you were unable to access Internet services
from the machine either?

Were you able to connect to the running PostgreSQL database via "psql"
or via PgAdmin III?

Were there any error messages in the postgresql log files?

What about ICMP ping? traceroute ("tracert" on Windows) to Internet
hosts? To your local gateway / nexthop router? etc.

 > We checked TCP connections using netstat.
> But there were not many TCP connections i.e it has not reached the max
> limit.

What is "not many" in this context?

Which limit? you know that the operating system imposes its own limit on
the number of TCP/IP connections that may exist, right? That limit
includes connections that are half-open or closing as well as regular
open/established connections.

> Java 1.6

Java SE 6? Java EE 6?

There is no such thing as "java 1.6".

--
Craig Ringer

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Murray S. Kucherawy"
Дата:
Сообщение: BUG #5837: PQstatus() fails to report lost connection
Следующее
От: Alex Hunsaker
Дата:
Сообщение: Re: BUG #5835: PL/Python crashes