Our Technical Support Portal has changed as we have moved to a new platform. Please visit support.quark.com to access your support tickets or to log a new ticket with us. All our existing customers should look for an email from email@example.com for activation of their New Support Account. If you face any difficulty in accessing the new portal, please write to us at firstname.lastname@example.org
In QuarkXPress Server there is a parameter to monitor subrendering routines called '-monitorsubrenders -queryinterval -noofretries -recycle'. This parameter is useful in the event QuarkXPress Server goes to a hang state. With these parameters defined, QuarkXPress Server monitors the subrender process and recycles it if it goes into the hang state.
You can set the monitoring routines for subrenderers using the following steps:
Windows Operating System:
For Mac OS:
These suggested parameters monitor the health check of the Subrenderers:
On the Windows Operating System, if a subrenderer is found to be hung during this time period, or if there is no change in memory during this time period, 'Master' kills the subrenderer, which then relaunches automatically. The recycle parameter is not mandatory on the Windows operating system to control re-launch of a Subrenderer.
On the Mac operating system, however, the 'monitorsubrenders' parameter is implemented with a recycle parameter only. The request will be killed only when a recycle parameter is given. If a recycle parameter is omitted, then 'master 'will not re-launch the hang process.
For the Windows operating system, the parameter works as described for the following scenarios:
In a case where the recycle parameter is not given, QuarkXPress Server monitors the memory usage and will recycle the Subrenderer if it is found to be in a hang state where there are no memory usage changes. ('-monitorsubrenders -queryinterval -noofretries)
If the recycle parameter is given, after the query interval and number of retries are
reached, then QuarkXPress Server will recycle the Subrenderer even if the request is being processed.
Example: '-monitorsubrenders -queryinterval -noofretries -recycle'.
It is recommended that the query interval and noofretries parameter be defined to match the worst case scenario when adjusting the query-interval to the longest time a request could possibly take in the current environment.