Purge Caches

[David Harrison]

Cloverleaf 5.6 on Solaris 10

We

Topic

[Jim Kosloskey]

David,

What release of Cloverleaf are you on.

I think there was an issue with purge caches on one release (perhaps 5.5).

We are on 5.6 and it works for us.

I believe if you have changed an Xlate (including doing a reconfigure) or any of the routing properties you will need to cycle the process. I would need to test the Xlate changes to be sure but for sure routing properties.

Also if you changed a Tcl proc (Tps or xltp) you can do a reload (at either the thread levels or the process level whichever makes sense to the situation).

If you add a new Tcl proc, then you can do a reindex followed by a reload.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[David Harrison]

Jim,

I’m on 5.6

I haven’t changed any routes. I’ve tweaked some Xlates, added a table and changed some tcl procs; and of course tested everything. I presume purge caches will reload all these.

[Jim Kosloskey]

David,

Purge Caches will not take care of the Tcl procs. If they are just changed you can do a reload in the NetMonitor (at the thread level or the Process level).

If the Tcl procs are new you will need to do a reindex first before the reload.

Again I am not sure about the Xlates (easy enough to test in Test before trying in Prod) but the Tables will be refreshed by Purge Caches.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[David Harrison]

Jim,

I tried purge caches in a test environment and it successfully loaded the revised Xlate. So I bit the bullet and did it in the production environment . . . looks good. I also reloaded the tcl procs just in case.

Thanks for your help,

Best wishes,

Dave

[Author]

Replies