> > On Wed, May 30, 2012 at 10:43 AM, Ramsey Gurley <[email protected]>wrote: > >> Given the way the pool is implemented, it is not fixable AFAICT. The EC >> is only connected to one OSC to run cleanup. So snapshots get inserted >> into all OSCs, but only get removed from one. The bigger the pool, the >> bigger the leak. >> >> Persistent session storage with multiple stateless instances should give >> the same effect without the leak though :-) >> > > How so? I'll be at WOWODC, so maybe I have to wait until then. > > Well, for database connections, it's essentially no different that having > multiple instances. One idea is that a new load balancer could be > implemented to skip instances that have an OSC locked. >
That would be awesome. > My app has potentially long running queries and the connection pool is > really necessary to keep it from blocking an instance completely. I don't > see how this would solve that. > > > I haven't used the ERXOSCPool beyond discovering it's leaky, but doesn't > the ERXEC factory round robin sessions off the pool? If you block up one > of the pooled OSCs, how are you not blocking the sessions connected to that > OSC? > Yeah, you still block in that case. If you have a small number of sessions (like I do) you are less likely to get in that situation.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
