Tom, Johan,
Ok, the problem is that PostgresDataSource does NOT pool connections.
I will work on this, but it won't happen overnight.
So in the meantime if you can work around it....
Dave
On Fri, 2002-06-14 at 09:27, Tom Lane wrote:
> Johan Svensson <johan.svensson@windh.net> writes:
> > where xaCon is the "pooled connection". Doing that I still get error if
> > I don't have the sleep() call between transactions. The PostgreSQL
> > console still prints a lot of "DEBUG: pq_recvbuf: unexpected EOF on
> > client connection" and one "FATAL 1: Sorry, too many clients already".
>
> The unexpected-EOF messages indicate the client side cutting the
> connection (and not bothering to send a terminate message first).
> I agree with Dave that this must be a problem inside the
> pooled-connection code --- somehow it's closing rather than recycling
> connections.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>