BookmarkSubscribeRSS Feed
Obsidian | Level 7

Hi, want to know more about in platform process manager. During restart if is renamed to js.events_backup, will that stop flow manager from starting? Why should we clear and cache to restart flow manager?

Amethyst | Level 16

Hello @raj231,


While it is "safe" to back it up by renaming, beware you will be losing the historic data of your executions (when you click "History").


Instead of that, I would rather make a copy of the file and trim the file, to a level of "last X days" or "last X months".


Consider as a database where it is recording your executions, and that is the data queried by FLow Manager when you click History. The more you remove, the more you won't be able to read anymore when you click "History". 


Additionally, you can consider to actually parse/read this data and create your own DB or SAS table, it might be useful, to analyse executions and compare performance, as good example.

Obsidian | Level 7

Thank you for the detailed explanation. But I would like to know why should we rename an existing file when we restart the process manager. As this was considered a solution whenever the platform process manager would not start giving out error messages. Please advise

Amethyst | Level 16

Hello @raj231,


I cannot give you the answer/solution to that question, since you probably better be asking it to whom provided you the solution.


What I can tell is that, if it this file is big enough, it might cause problems as:

  • slowness loading the history of executions
  • JVM errors
  • timeouts
  • and such...

The reasons is that this is a text file, which is read/wrote and loaded in sequential basis, hence some periodic maintenance in this file would help you with the health of this service.

Please note the fact I mentioned "periodic maintenance": always healthier to act pro-actively than react to errors.


Anyway, this is only for the Flow Manager, a client application. Just to be clear, should not affect the availability of your server, just the client (because it is Java based)


suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 2 in conversation