[OGo-Users] postgres connection limit exceeded

[Helge Hess]

On 07.03.2008, at 03:18, Adam Tauno Williams wrote:
> On Fri, 2008-03-07 at 00:33 +0100, Helge Hess wrote:
>> BTW: I checked. OGo does *not* keep the connections open, so its  
>> not 1
>> connection per session. There is a timeout which closes connections
>> after some time.
> Potentially stupid question:  why does OGo need to open a connection  
> per
> session in the first place?  Why can't/doesn't each session just use
> (and share) a common connection?   My understanding is that OGo  
> (SOPE?)
> serializes requests, only doing one-at-a-time.

I think the original reason was the layering of EOF(1) (or a  
misunderstanding of it). OGo would open an EODatabaseChannel to track  
objects which then would open an EOAdaptorChannel to do the connection.
Technically this isn't required and I think there is no good reason to  
do it this way. The EODatabaseChannel should acquire/release adaptor  
channels on demand.

That SOPE (currently) serializes requests doesn't matter that much  
from a design perspective. We wouldn't want to restrict things to a  
one-channel design.
It basically requires a proper connection pool (in JOPE this is  
actually done by the EOAdaptor in a thread safe way).

Greets,
   Helge
-- 
Helge Hess
http://www.helgehess.eu/