Regarding server bounces, I’ve noticed a haphazard assortment of processes. In an IDEAL shut down situation, the steps I’ve been preaching to our clients are:
- In the Admin Console, log in to Stop the workflow agent(s)
- This will pause the workflow queue. Currently running workflows will continue as normal, but no new workflows will be processed. Queued workflows are stored in a DB table and will still exist when the agent is restarted / server is restarted.
- Validate the following BEFORE shutting down
- Users have logged out of the system
- No currently running workflows
- Extended formula queue is empty (Performance Monitor in admin console or via SQL query)
- Shutdown each server
- Option 1: <serverURL>/html/en/default/admin/shutdown.jsp
- Option 2: Run the shutdown.sh script or windows bat file
- Validate shutdown by:
- The server.log file should have a line that reads “Shutdown complete”
- The system process should no longer be running.
If any of the validations above fail, it’s typically no big deal, but it would be good to double check.
Taken from TangoMC Smart Hub
No comments:
Post a Comment