On Wednesday 20 August 2008 14:05:08 Mick Semb Wever wrote: > > // acceptable for sesat not to have to have a user > > service backend > > - LOG.debug(ne.getMessage(), ne); + > > LOG.warn(ne.getMessage(), ne); > > If you look through the history (r6031) you will see that it used to be > warn/error but was changed to debug. > This will write a warning _every_ request > (the /normal/ failure doesn't result in the 5 second wait) > and cause enough damage to the logs to be another production crisis. > > ~mck
I was probably a bit to fast with that commit, but I think we should look for another solution then to use exceptions to catch something that is allowed. And the reason is basically that it could mask more serious problems like the ones that we have had today. (Every search took 5 seconds) Should there be a property that disable/enable this? Could this service come and go in the lifetime of the running application? Håvard _______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
