Launching Mode Differences and QuarkXPress Server System Types

Our Technical Support Portal has changed as we have moved to a new platform. Please visit to access your support tickets or to log a new ticket with us. All our existing customers should look for an email from for activation of their New Support Account. If you face any difficulty in accessing the new portal, please write to us at

Launching Mode Differences and QuarkXPress Server System Types

In Single Application mode, all the requests related to the Admin and are document specific are taken care of by QuarkXPress Server itself. However, if you are running QuarkXPress Server in Master-Subrenderer mode, all the Admin requests are taken by the Master and the layout-specific requests are handled by the Subrenderer.
There are two different ways to run in  Master – Subrender mode:

  1. Launching by Keepalive.bat: In this case, if the Subrenderer crashes, then the .bat file restarts both the Master and the Subrenderer without administrator interaction.
  2. Launching by using a parameter “-monitorsubrenders”: In this case if a Subrenderer is found to be hung, or if there is no change in memory during this time period,  the Master kills the Subrenderer process, which then relaunches automatically. The value should be specified in the QuarkXPressServer.config file in

    COMMANDLINE= -subrenders 2 -monitorsubrenders –queryinterval 600 –noofretries 20 –recycle

Note: The meaning of the other values in the COMMANDLINE entry:

Queryinterval: The time in seconds before sending the next request to the Subrenderer.
Noofretries: Number of Retries sets the Subrenderer before restarting the process.
Recycle: This will restart the process if it goes into a hung state.

Was this answer helpful?YesNo
Topic Information
  • Topic #: 30026-1778
  • Date Created: 11/20/2012
  • Last Modified Since: 11/20/2012
  • Viewed: 1116
Welcome Guest