Perhaps the thing to do here is to have a simple message on start-up that says:
"Broker starting ..." "Broker started successfully." And then no other output unless specified. William ----- "Alan Conway" <acon...@redhat.com> wrote: > Robert Greig wrote: > > 2009/1/1 William Henry <whe...@redhat.com>: > > > >>> What is the rationale for this? It seems a very bad idea to me - > >>> which > >>> other standard processes behave like this (httpd does not, for > >>> example). > >>> > >> Good question. One of the desirable properties of message brokers > and > >> other messaging technology is high performance. Eliminating any > >> unnecessary writes, even to standard output, is important. You'll > find > >> that many messaging technologies will have as little or no logging > output > >> going to files or standard out by default. It can always be turned > on if > >> needed and there is usually another more efficient mechanism in > place. > > > > It is certainly important not to write to stdout during the > "critical" > > flows, i.e message ingress and egress. However that is clearly not > > what I am talking about. I am referring to the fact that on startup > by > > default the broker does not emit any information to indicate that > it > > has started successfully or which ports it is listening on. I find > > that quite bizarre and unhelpful. > > > > RG > > > Try running the broker with --log-enable=info+ - if you think that > gives > reasonable output we can easily change the default. I don't think > there is any > per-message info level logging, and if there is it should probably be > removed. > > Cheers, > Alan.
