D
Dale
I need some kind of heap analyzer tool or something that will tell me
what Objects are not getting collected by the GC. The program starts
a bunch of objects, and each object runs in it's own thread. The test
objects usually makes a connection of some type, and does a test. At
the end of the test, or at a timeout, each one of those objects calls
back with the result of the test. These tests are scheduled every 20
minutes. In each of these test objects, the run method stops after it
reports back, and that should be it. But in Windows NT processes, I
see this program takes up more and more memory as the days go by (it's
up to 74,732K at the moment). If I stop and restart, it settles at
about 18,000K, but slowly makes it's way up to that 75,000K range
after a couple of days.
Is there a way to list the objects the JVM thinks are still active?
--Dale--
what Objects are not getting collected by the GC. The program starts
a bunch of objects, and each object runs in it's own thread. The test
objects usually makes a connection of some type, and does a test. At
the end of the test, or at a timeout, each one of those objects calls
back with the result of the test. These tests are scheduled every 20
minutes. In each of these test objects, the run method stops after it
reports back, and that should be it. But in Windows NT processes, I
see this program takes up more and more memory as the days go by (it's
up to 74,732K at the moment). If I stop and restart, it settles at
about 18,000K, but slowly makes it's way up to that 75,000K range
after a couple of days.
Is there a way to list the objects the JVM thinks are still active?
--Dale--