> 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 (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
