generally OJB has no memory leak. We made several stress tests before release a new version.
Except if you are using the "per thread metadata change"-feature provided by MetadataManager and you use for each thread a new copy of the repository. This is fixed in CVS head (The final 1.0 is coming soon).
[EMAIL PROTECTED] wrote:
Hi, I also saw my application slowing down with the number of inserted objects. I am using the ODMG layer.
I have an application which has to insert different sets into different tables; each set is in its own file. Each time after inserting a set of objects I set every known reference to null.
Can you describe more detailed what you are doing. Especially the usage of OJB. Pseudo code example will be helpful.
regards, Armin
I called Runtime.getRuntime().runFinalization() as well as System.gc(); after this I closed and reopened the database connection. So I think I shold have started with the same amount of memory as before. In spie of this, (Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory()) grew every time.
I have tried to stop the application and start new every new set; this is less memory-consuming. But even more interesting: the insert of the14th set (150000 objects) took only 8 minutes - compared to 40 minutes before! However, it should not be like this, should it?
Any ideas what to do within my application? Thanks, Birgitta
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
