Cloudname/cloudname — pull request #39 by borud (2012-01-02 14:33:28+00:00)
Title: Removed explicit logging in Archiver

* Originally the archiver was written to deal with log messages in the
log server. Since the log server *never* deals with log messages
generated by the internal java.util.logging hierarchy in the JVM
where it runs, but log messages that arrive over the network, this
was never a problem. However, when used to deal with log messages
that originated in the same JVM, we get a problem with looping
behavior.

* Removing explicit logging in the archiver code itself is the first
step. The archiver may call code that is not under our control which
will write log messages. These too will have to be supressed.
There are two possible methods for doing this. One is to inspect
the call stack of the logging code. This might have severe
performance implications. The other is to just grab the Logger
instances of known loggers and adjust their log filtering so no log
message will get through.

* Before you make suggestions on how to fix this I expect you to know
how java.util.logging works and that you have read through at least
parts of the java.util.logging implementation. I'm not kidding.