Hi again Chris,
> Hi Armin, > > Armin Waibel wrote: > > > > > Which connection pooling? Using the intern connection pooling or using > > datasources > > from a pool outside of OJB? > > The internal connection pool. Connections were continually acquired until the > pool limit was reached. When I set eager-release to 'true' the problem went > away (but then I got a different one of the transaction not committing before > the connection got closed, so I lost my updates - hence the hack fix I > suggested). When using the OJB internal connection pooling use the default (original, no need to change properties) OJB.properties. Your problem seems to be a user-do-the-wrong-thing problem ;-) Full version of OJB shipped with a stress test were 10 threads at the same time handling 2000 objects per thread (store, fetch, delete each object) and this test passed well (call bin\build.bat performance2). When using the PB-api don't forget to call PB.close() after using a PB instance (close() returns instance to pool). HTH regards, Armin > > Cheers, > > Chris > > > > -- > To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org> > > > -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
