Robert, I've monitored orion using jprobe when orion is started with the -restart command.
It loaded another copy of the application classes in a new classloader, and eventually ran out of memory. I never pursued this as i had higher priority things to work on at the time. Not sure if the original classloader was eventually cleaned up, or whether there is some config setting that causes Orion to work differently. Greg. ----- Original Message ----- From: "Robert Krüger" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Sunday, March 10, 2002 9:06 PM Subject: Memory leak with linux jdk1.4 - orion 1.5.4 > > hi, > > I'm experiencing serious problems with a memory leak that causes orion to > consume more memory with each application restart/redeployment with the > combination jdk1.4 (linux) - orion 1.5.4. with jdk 1.3 memory consumption > remains constant after a while. even calling System.gc() explicitly doesn't > help. has anyone else seen such behaviour? based on these observations it > appears more likely to be a VM bug rather than an orion problem. is this a > known problem? has anyone tried to narrow it down by using a profiling tool? > > tia > > robert > >
