Hi John,

we are using Charts API for creating charts in our application..

Its creating some temp image files for that.. To delete those files, we have put a java.util.Timer (scheduler) object to delete the files from that directory at the scheduled interval

In this deletion code, we have put a check for the tmp/deploy directory check also..

so that whenever the war file is undeployed and that directory is deleted from the temp/deploy folder.. cancel the scheduler as with the new deployment, the new scheduler will be created..

This cancel of the scheduler on undeploy was working perfect fine with JBoss 4.0.3

But now with JBoss 4.0.5, when we are trying to cancel the task, its saying the reference of the timer object is already null.. but still the scheduler task is runing in JBoss.

at the start init of the timer, we are getting the exact path of the tmp/deploy directory for our war file..

and with each scheduler run() method call, we are checking if that directort exist..

if it exist, check the impage dir and try deleting the files from their..

if the directory don't exist(meant war file undeployed), cancel the scheduler task..

Now somehow, when we are running the task, the JBoss is taking control of the timer instance and making our application specific object null.. so we are not able to cancel the scheduler when the war file is undeployed..

Due to that, if I undeploy/deploy the war file 3 times, I will be having the 3 schedule tasks running... 2 will be from previous deploy

So until the server is restarted, the previous 2 will not be killed..

Can you please help me solve this issue...