System Administration - eXist: A NoSQL Database and Application Development Platform - page 387

Logfile Description

ehcache.log When using Ehcache with eXist, the Ehcache log messages are redirected to this file. Ehcache in eXist at this

time is not recommended for general use.

betterform.log When using betterFORM as your XForms engine in eXist, the log messages of betterFORM are redirected to

this logfile. It can be useful for assisting in developing and debugging XForms applications.

restxq.log If you are using RESTXQ in eXist, then all operations of the RESTXQ framework and server are logged here,

including any issues with compiling your XQuery. Note that when your XQuery runs, any log messages it
produces will be sent to exist.log .

backup.log All log messages related to creating database backups or restoring database backups are written to this file.

mdStorage.log If you are using the new metadata storage module, then any log messages generated by this module will

be written to this file. For more information on the metadata module, see metadata .

The logfiles in eXist are all plain text, so you may view them with any plain-text edi‐
tor. If you prefer a GUI tool with colored highlighting of the log levels, then Apache
Chainsaw may be worth a look.

On Unix/Linux/Mac systems, you can monitor log messages by
tailing and following the appropriate logfile. For example:
tail -f $EXIST_HOME /webapp/WEB-INF/logs
On Windows systems, you can configure log4j to log to the Win‐
dows Event Log if you wish by using org.apache.log4j.nt.NTE
ventLogAppender . See the log4j documentation for the exact
configuration details.

JMX
Java Management Extensions (JMX) is a Java technology that allows an application to
expose monitoring information and management options to other applications. eXist
acts as a JMX server and can service requests from any JMX client. At present, eXist
mainly exposes monitoring information and very little in the way of management
services via JMX. To use eXist with JMX, you must enable and configure JMX via
options passed to the JVM when you start eXist.

If you are using either $EXIST_HOME/startup.sh or $EXIST_HOME/startup.bat for
starting eXist, you can just pass the additional -j argument with a TCP port number
for the JMX server to listen on. For example:

$EXIST_HOME /startup.sh -j 1099