Hi Bobby,
Bobby Lawrence wrote:
When does OJB release the objects it creates to be collected by the garbage collector?
This should happen after the use of a OJB method. OJB doesn't (shouldn't) hold "strong references" to persistent objects.
I have an app that uses a session bean. This session bean controls all the OJB persistence, but it seems that the memory used by my app server continues to grow...only when using OJB....
Is there a setting I can use to control this?
Currently, I have the no cache attribute set in my connection descriptor:
<object-cache class="org.apache.ojb.broker.cache.ObjectCacheEmptyImpl"/>
I made a test insert/update/query/delete 50 objects (using the odmg-api, this api use the PB-api internally) in a non-managed environment. The test run 100 times in a loop using a profiling tool, the VM heap size used by OJB doesn't increase (if you interested I can send you some reports).
Did you check the session-pool settings of your application server (pool size, active objects, ...).
Did you check your code, do you always close the used PB instance?
regards, Armin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
