...
In run-server.sh, change the exec java to something like:
Code Block |
---|
exec java \ -Xmx1024M -Xms512M -XX:+HeapDumpOnOutOfMemoryError\ -Dorg.eclipse.jetty.level=ERROR -Dorg.eclipse.jetty.websocket.level=ERROR$DEBUG_FLAGS \ -Djava.util.logging.config.file=/home/wave/wiab-logging \ -Djava.security.auth.login.config=jaas.config \ -Dwave.server.config=server.config \ -jar dist/waveinabox$NAME-server-$WAVEINABOX_VERSION.jar |
The -Djava.util.logging.config.file=/home/wave/wiab-logging
is the only new line.
I have deliberately, turned down the logging from jetty to ERROR only, so that the log fills up with Wave only messages.
Then create the logging configuration file at the path specified:
Note |
---|
TODO: make this only change logging for Wave. |
Code Block |
---|
handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler
.level = ALL
java.util.logging.ConsoleHandler.level=ALL
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
org.waveprotocol.level=ALL
|
...
Since the logs consist of huge quantities of almost the same message, dictionary compression schemes work incredibly well on it. So please compress it with something before uploading.
(Anecdotally, a 224M log file compresses to 1.9M using xz)!
Jetty Logging
Since Jetty 9, the logging implementation in Jetty has changed to have a more extensible backend.
The settings have become completely independent of the rest of the logging settings. To set them, change the run-server script to pass the following flags:
Code Block |
---|
-Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog \
-Dorg.eclipse.jetty.level=INFO \ |
For more information, refer to the Jetty9 documentation.
Disable Logging
TODO: write about it here, it simply consists of removing the lines from run-server.sh