Hi Rohit,The purgeOldJobs service can only be run one at a time so the error below just indicates that the queued service execution timed out while waiting for the existing execution to complete. I can think of two possible causes for this: 1. Your JobSandbox table has for some reason grown to be exceptionally large and the service is struggling to clear the old records before the next scheduled service execution. Assuming the service is actually making progress then you should be fine to just keep it running. 2. The ServiceSemaphore table which controls the semaphore flags has a stale record for the purgeOldJobs service and is locking the service even though it isn't being executed. I may be wrong but I think the ServiceSemaphore table isn't properly cleared when OFBiz is restarted meaning that any semaphore locks in place when OFBiz is stopped get left behind and prevent those services from running after the restart. Removing any ServiceSemaphore records for services that aren't currently running should resolve the problem.
Regards Scott HotWax Media http://www.hotwaxmedia.com On 30/12/2009, at 9:25 PM, rohit wrote:
Hi I upgraded to the latest SVN, and am getting the following error when running the purgeOldJobs service. I tried to look for more details in my logfile but could find more than that mentioned below: Request scheduleService caused an error with the following message:<li>Service dispatcher threw an exceptionService [purgeOldJobs] with waitsemaphore exceeded wait timeout, waited [307.608], wait started at 2009-12-30 02:47:04.374The problem probably is with my database, as the service is working fine ona new build with seed data, but not when old data in imported in the currenct SVN. i am using postgres as the database. any help will be sincerely appreciated. Thanks -- View this message in context: http://n4.nabble.com/Error-in-purgeOldJobs-service-tp990793p990793.html Sent from the OFBiz - User mailing list archive at Nabble.com.
smime.p7s
Description: S/MIME cryptographic signature
