You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Enable ALL logging

TODO: document the logging levels available.
By requesting Java uses a logging configuration file, we can easily configure the logging level to more than the default. (Default depends on whether WIAB was compiled in demo mode or not).

In run-server.sh, change the exec java to something like:

exec java \
  -Xmx1024M -Xms512M -XX:+HeapDumpOnOutOfMemoryError\
  -Dorg.eclipse.jetty.level=ERROR -Dorg.eclipse.jetty.websocket.level=ERROR \
  -Djava.util.logging.config.file=/home/wave/wiab-logging \
  -Djava.security.auth.login.config=jaas.config \
  -Dwave.server.config=server.config \
  -jar dist/waveinabox-server-$WAVEINABOX_VERSION.jar

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:
TODO: make this only change logging for Wave.

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

Then upon rebooting your server, the amount of logging information should be dramatically increased. I suggest pipeing it to a file from here.

Uploading logs

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)!

Disable Logging

TODO: write about it here, it simply consists of removing the lines from run-server.sh

  • No labels