thanks. I wasn't aware of the PeristenceBrokerPool concept.
regards Tino
Armin Waibel wrote:
Hi Tino,
Tino Sch�llhorn wrote:
Hi,
I am using OJB(cvs head from 2 weeks ago) in Tomcat 5.0. There I have several PersistenceBroker which I close after each request with PersistenceBrokerFactory.realeaseAll().
Why you do that?
This will kill the PB pool (PB pool NOT connection pool) each time you call it.
After some time I get the following error:
Maybe it's because you kill the PB-pool or you don't close the PB instances after use with PB.close() and the PB-pool gets exhausted.
...
But the thing is: I don't even use connection pooling (or so I think). I activated the line
ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryNotPooledImpl
in the OJB.properties file. So I think, that ConnectionPooling is switched off. Or do I have to change these settings in the connection-descriptors?
Do you have any suggestions?
If you don't want to use Connection pooling set the property in OJB.properties (you do that). Now connections will not be pooled. Connections will be closed after use on PB.commitTransaction, PB.abortTransaction or PB.close().
So if you need a PB instance get it from PBF, do your work and *close* the used PB instance (internal OJB return the used PB instance to PB-pool).
regards, Armin
Tino
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
