We recently ran into a problem where the garbage collection (GC) process would no longer run (our WWSTATE file contained over a million records!, and the application response time was abysmal).
There is a control record VERSION in the file WWCONTROL which contains a date & time that GC is next due to run. The date field was set to zero (meaning everyday) and the time field was set to 86397 (23:59:57). According to the WWLOG file, the last completed run of GC was at 22:59:57 (GC was set to run at the default value of every 60 minutes). It seems to me that there is probably a bug in the redback code that determines whether it is time to run GC or not. If the process doesn't run in the three seconds between 23:59:57 and midnight, then the current time will never be after 23:59:57 and therefore GC won't run - this seems to be the case for us. Has anyone else come across this problem? And what was your solution? I've heard of someone setting up a cron job to tidy up the WWSTATE file. I've altered the GC parameters to run every 1 day instead of every 60 minutes. Hopefully this will fix the problem as the VERSION control record now contains an actual date (tomorrow) instead of zero. AdrianW DISCLAIMER: Disclaimer. This e-mail is private and confidential. If you are not the intended recipient, please advise us by return e-mail immediately, and delete the e-mail and any attachments without using or disclosing the contents in any way. The views expressed in this e-mail are those of the author, and do not represent those of this company unless this is clearly indicated. You should scan this e-mail and any attachments for viruses. This company accepts no liability for any direct or indirect damage or loss resulting from the use of any attachments to this e-mail. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
