cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Larsen" <>
Subject Memory leak scheduling job from java
Date Thu, 12 Jan 2006 19:43:45 GMT
I'm using Cocoon 2.1.7 and have set up a schedule to run every minute by
setting up a trigger in cocoon.xconf:

 <trigger name="com.envisn.nv.config.ConfigurationManager"
    <cron>0 0/1 * * * ? *</cron>  <!-- every minute -->

The trigger executes a class that manages the scheduling of a job, and if it
needs to, it adds a new entry:

  JobScheduler scheduler =

  SynchronizerDaemon daemon = createSynchronizerDaemon(context);
          daemon, minutes, false, null, null);

The job runs on schedule perfectly but there appears to a problem with the
job execution releasing resources.  Each run of the job adds to the memory
consumption and eventually will create an out of memory error.

I tried to track down the memory leak with JProfiler.  I had the app run the
job only once and after execution the resources that were created when the
job started still exist.  Here are a few lines from the allocation call tree
that was created from the job:

  80.6% - 44,761 kB - 661,134 alloc.    
   80.5% - 44,738 kB - 660,138 alloc.
    79.9% - 44,375 kB - 654,219 alloc.
     79.9% - 44,375 kB - 654,219 alloc. 

I tried 'scheduler.removeJob(jobName)' to see if that would free resources
without any effect.

Is there something else that needs to be done to have these resources

Thanks for any advice,

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message