#1121
- Created on2011-08-17 17:12
- Reported by
- StatusFixed
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
Improve Slf4jEventHandler
instead of logging always to the akka.event.slf4j.Slf4jEventHandler logger, the 'instance' should be used to find a more appropriate one.
Leave a comment
on 2011-08-29 12:13 *
By Patrik Nordwall
Assigned to changed from rkuhn to Patrik Nordwall
Status changed from New to Accepted
I'll fix this.
Note that you should retrieve the SLFLogger from the incoming instance.getClass.getName, not with Logger(this.getClass.getName).
Then the class name should not be part of the log message at all.
The stackTrace shouldn't be part of log message either. Use log.error(msg, throwable)
Note that you should retrieve the SLFLogger from the incoming instance.getClass.getName, not with Logger(this.getClass.getName).
Then the class name should not be part of the log message at all.
The stackTrace shouldn't be part of log message either. Use log.error(msg, throwable)
(In revision:7da2341bedac63debc8830c86829fff5ec6edac4) Use slf4j logger from the incoming instance.getClass.getName. Fixes #1121
Branch: master
- Different logger based on incoming event.
- Removed format, since that should be in logback configuration.
- The stackTrace is now logged with the error(msg, throwable) method.
Branch: master
Updating tickets (#967, #974, #975, #976, #980, #981, #989, #990, #992, #993, #994, #999, #1000, #1004, #1008, #1011, #1015, #1018, #1022, #1023, #1024, #1025, #1027, #1028, #1029, #1030, #1032, #1033, #1036, #1047, #1053, #1062, #1067, #1068, #1069, #1072, #1075, #1078, #1082, #1102, #1107, #1110, #1111, #1115, #1116, #1121, #1122, #1123, #1124)