Skip to main content

MarkView Application Server - Properly Stopping Apache iAS and MarkView Application Server Processes



Applies To

  • ERP System: Oracle
  • MarkView Version: Versions prior to MarkView 6.x


It is important to properly stop processes in order to ensure correct database session cleanup. Following is the correct method for stopping Apache iAS and OC4J and MarkView Application Server processes.


  1. In general, for Apache iAS: apachectl stop
  2. For OC4J / MarkView Application Server:
    java –jar admin.jar ormi://<rmi_port> <admin username> <admin password> –shutdown
  3. If the operating system processes do not properly shut down using these methods, it may be necessary to terminate the process manually.
    In a Unix environment, a System Administrator will typically issue a 'kill' command for the process id. E.g.: kill 136
    Some Administrators may want to resort to a forced kill (kill -9) if the process does not respond to a normal kill command. That approach is NOT recommended.
    The default for a kill command is kill -15. If the process does not respond to this kill level, attempt the following parameters in this order:
    kill -2 <pid>
    kill -1 <pid> ***
    kill -3 <pid>
    kill -9 <pid>
    *** If the process does not respond to 'kill -1', the next step should be to determine the database sessions corresponding to the process, and kill those database sessions BEFORE proceeding to 'kill -3' or 'kill -9'.
    This step is important, as these database sessions may not be cleaned up properly by the operating system process if it is terminated with a 'kill -3' or 'kill -9'. (The Unix commands 'kill -3' and 'kill -9' force the process to core dump or exit, respectively, without any chance to cleanup processes.)

Keywords: apache