Comments on: Clearing the Process Scheduler Cache – without a Reboot

By: Jules

Jules — Tue, 17 May 2011 23:55:18 +0000

FYI, I’m running PT 8.43 at the moment and had some changes in an App Package that weren’t being recognised, no matter what I did. Deleting the cache was the only option.

By: Hugo

Hugo — Wed, 25 Feb 2009 16:48:55 +0000

I am running App Engine processes in PT 8.49.18 and having severe issues with the system not recognizing changes to the App Engine. I changed SQL, PeopleCode, deleted and resaved and nothing seems to change. I have to re-create my app enginge to get the system to re-read the information. Apart from clearing the cache on the process scheduler, which you mentioned, is there anything else that has come about that we can do?

By: digitaleagle

digitaleagle — Wed, 31 Oct 2007 13:11:21 +0000

One of the biggest reasons for clearing the cache for App Engines is because the system doesn’t seem to recognize changes to SQL. In my experience, if you change PeopleCode in an App Engine and re-run the process, it uses the new PeopleCode. But, if you change SQL and re-run the process, it uses the old SQL before the change.

One trick I have learned is that if you change the structure of the App Engine steps or actions, it will make the system re-read all the SQL instead of using what is in the cache. I used to add a step, save the program, delete the step, and save one more time. But, even easier, you can just uncheck the active flag for one step, save, re-check the active flag, and save one more time.

So, out of habit, I uncheck the Active flag, make my SQL change, save the program, re-check the active flag, and save. This way, I have very little problem with cache during App Engine development.

I built this habit in PeopleTools version 8.46, but I have noticed that I don’t have to do it in PeopleTools version 8.49.