Re: Concurrent Connections - User only allowed one

From: Craig Moon <sysadmin(at)usight(dot)com>
To: Gordon Ross <G(dot)Ross(at)ccw(dot)gov(dot)uk>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Concurrent Connections - User only allowed one
Date: 2003-10-03 14:20:41
Message-ID: 3F7D85B9.30907@usight.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

You can turn on connection logging by editing postgresql.conf and
uncommenting the line

log_connections = false

and setting it to true.

Gordon Ross wrote:

>I've double checked the code, and it gets one connection to the db
>"dbCon = DriverManager.getConnection(dbURL, dbUser, dbPassword);", and
>just re-uses that. Before it attempts to get a connection, it checks to
>make sure it doesn't already have a connection, and that's it.
>
>Is it possible to get PG to log connection attempts, so I can double
>check ?
>
>Thanks,
>
>GTG
>
>
>
>>>>Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk> 03/10/2003 13:21:09 >>>
>>>>
>>>>
>
>On 03/10/2003 11:35 Gordon Ross wrote:
>
>
>>OK. I increased it from the default of 32 to 128 and did a pg_ctl
>>reload. Still get the same problem. With server running (but doing
>>nothing), cannot connect from PC, I get the error message: "No
>>pg_hba.conf entry for host 192.168.24.108" - yet shutting down the
>>server process allows the PC to connect.
>>
>>
>
>Wierd. It sounds like your server program is grabbing every possible
>tcp/ip connection to the db. Could this be the case somehow? You would
>
>still be able to psql to the db from the Solaris box as there are
>usually
>a couple of reserved super-user connections. I can't explain why you
>get
>that particular error message though.
>
>
>
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Tom Lane 2003-10-03 14:24:47 Re: Concurrent Connections - User only allowed one
Previous Message Dave Tenny 2003-10-03 13:34:28 Re: Row Lock