About Stopping the SIMULIA Execution Engine Server

If you cannot gracefully shut down the SIMULIA Execution Engine using the WebLogic administration tools, you can resort to terminating the process in your operating system.

Each WebLogic server instance runs in its own JVM. It is highly recommended that all SIMULIA Execution Engine WebLogic servers be shutdown gracefully through the Administration Console. If you are unable to gracefully shutdown a server in this way, you can terminate the server JVM using the following methods:

  • Windows: Type Ctrl-C in the Command Prompt window that you used to start the server, or use the Windows Task Manager to terminate the associated Java process.

  • Linux: Use the ps command to retrieve the server instance Java process ID, and use the kill command and the process ID to terminate the JVM.

Important: Terminating the JVM stops the server immediately and may lead to a loss of data.

It is usually not necessary to stop running jobs before stopping the SIMULIA Execution Engine. Jobs that are running at the time of the shutdown are suspended until the SIMULIA Execution Engine is restarted. However, not all jobs survive a restart—if large file transfers are in progress, they may fail. If work items were assigned to stations and do not complete before the shutdown, they will not resume.

Individual work items in a job that are in progress on stations may continue to run uninterrupted when the server is shutdown. However, the job workflow will not progress until the SIMULIA Execution Engine is restarted.

It is important that stations that are running work items at the time of the SIMULIA Execution Engine shutdown not be terminated or themselves shutdown until after the SIMULIA Execution Engine has been restarted. Terminating a station that is running work while the SIMULIA Execution Engine is shutdown will cause the job to hang or fail. Stations that are running no work at the time of the shutdown can be terminated safely at any time.