Logging could be cleaner
Reported by Ben Hood | February 4th, 2011 @ 06:47 PM
The current logging could be cleaner than it currently is. For example:
-
The stdout log is polluted with lots of stack traces that really should only go into the file log. The stdout log should only contain a 1-liner to indicate that there was an error.
-
akka shouldn't log this kind of stuff - we should probably add a suitable config file for it:
2011-02-04 18:14:03,180 WARN
Can't load 'akka.conf'.
One of the three ways of locating the 'akka.conf' file needs to be defined:
1. Define the '-Dakka.config=...' system property option.
2. Put the 'akka.conf' file on the classpath.
3. Define 'AKKA_HOME' environment variable pointing to the root of the Akka distribution.
I have no way of finding the 'akka.conf' configuration file.
- This kind of log entry is fairly meaningless - it should probably reference a class, but in the tersest way possible:
2011-02-04 18:16:45,166 INFO Stopped actor for key: pair1
2011-02-04 18:16:45,370 INFO Started actor for key: pair1
- On a case by case basis, this kind of thing really needs to get rooted out - the error message is pretty much useless so the actual log statement needs to get cleaned up:
2011-02-04 18:16:45,577 ERROR 500
2011-02-04 18:16:45,618 ERROR 500
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.