Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
- Subject: Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
- From: Mike Schrag <email@hidden>
- Date: Fri, 23 Apr 2010 04:22:36 -0400
> er.extensions.ERXJDBCAdaptor.className=er.extensions.jdbc.ERXJDBCAdaptor
> er.extensions.ERXJDBCAdaptor.useConnectionBroker = true
> er.extensions.ERXJDBCAdaptor.switchReadWrite=false
> er.extensions.ERXDatabaseContext.className = er.extensions.eof.ERXDatabaseContext
> er.extensions.ERXDatabaseContext.activate = true
> dbMinConnectionsGLOBAL=1
> dbMaxConnectionsGLOBAL=5
> dbConnectionRecycleGLOBAL=1.0
> dbMaxCheckoutGLOBAL=86400
Unless you're doing direct JDBC access, i'm pretty sure using the connection broker with multiple db connections isn't really doing anything for you. You would still have a dbctx lock on the whole thing. What you probably want is the object store coordinator pool. The trade-off here is potentially duplicating snapshots in each coordinator and using more ram.
# er.extensions.ERXObjectStoreCoordinatorPool.maxCoordinators = 0
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden