so if you are not using an app server, what's the best way to work with the connection pooling mechanism? I set eager-release to be true to avoid the connection pool continually growing; basically I was getting a "could not retrieve a connection" error because the pool just grew to beyond the configured limit. I was reluctant to simply increase the pool size as it wasn't obvious that it would just keep growing, and if my app ran for long enough that it wouldn't just fill up again at some point..
Also is it actually possible to retain the connection throughout, say, a user session rather than a new one being grabbed from the pool every time a statement gets executed? Maybe if I'm not using an app server then I shouldn't be using the connection pool (I don't have a seperate transaction manager as I'm not using an app server, so I need to rely on the transactions provided by JDBC and I want the connections open across a session). Cheers, Chris Matthew Baird wrote: > eager-release is for j2ee. We can, and should, release the connection to the pool as >soon as we can, and rely on the pooling mechanism to give us back a new connection >when we need it. > > Inside the app server, the close on the connection doesn't really close the >connection, just returns it to the pool. > > cheers, > Matthew -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
