Hi!
We are running OJB on our production serveur (tomcat 4.1.30 in this case).
The JVM was running troubles after running a while so I've modified my app to count objects that are loaded : we have a static Map (key=class.getName(), value=count) that counts the total number of live instances of a particular class. Typically, our beans increment the counter for their own class in their constructor, and decrement it in void finalize().
On our dev + staging environments : no problem.
But on our production server, it appears that somehow, there are more instances of beans that I believe it should.
Typically, we have a "company" bean which maps directly to Oracle's table SMJ_COMPANY. There are 1012 lines in this table. But we get more than 7000 instances of bean company after a while.
Some other tables have much much more lines.....
Garbage collecting doesn't do anything to it.
Is this abnormal? Do you think this can explain our JVM growing forever in memory?
Thank you for your help!
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
