2017

Table Of Contents
GETTING STARTED WITH QUARKXPRESS SERVER
A Guide to QuarkXPress Server 2017 | 7
The same application preferences (each renderer has its own preferences files,
but QuarkXPress Server keeps them synchronized)
The same document cache in memory
The same memory cache
The same server XTensions modules (a separate instance of each XTensions
module runs with each renderer)
The same server document pool (if defined in the QuarkXPress Server
preferences or if a document provider is used in place of the document pool)
If a renderer unexpectedly quits, the master QuarkXPress Server restarts the renderer
without requiring any action from you.
Changing logging levels in “log4j2.xml“
You can change the logging levels for QuarkXPress Server. Options include ERROR,
INFO, WARN, DEBUG, and TRACE.
ERROR = includes messages that indicate disrupted and failed requests.
INFO
= includes messages that indicate the state of services.
WARN
= includes non-critical service error messages
DEBUG
= includes messages that indicate server resource usage.
TRACE
= includes messages according to activity related to requests.
Refer to Java documentation for more information about logging levels.
To change logging levels:
Open the “conf” folder in your QuarkXPress Server folder.
1.
Open “log4j2.xml” in a text-editing application.2.
To define the logging level for QuarkXPerss Server errors, scroll to <logger3.
name=com.quark.qxps. The structure is as follows:
<logger name=”com.quark.qxps”>
<level value=”ERROR” />
</logger>
To define the logging level for QuarkXPress Server transactions, scroll to4.
<logger name=QXPSTransactionLogger. The structure is as follows:
<logger name=”com.quark.qxps” additivity=”false”>
<level value=”INFO” />
<appender-ref ref=”QxpsTransactionFileAppender” />
</logger>
To define the logging level for other activity, scroll to the <root>. The structure5.
is as follows:
<root>
<priority value=”ERROR” />
<appender-ref ref=”QxpsServerAsyncAppender” />
</root>
Save and close “log4j2.xml.”6.