Hi.
I've always been annoied that Exceptions in Schedule.schedule() are not logged with stack-traces.
I maintain this code i a separate branch we use:
@@ -151,7 +151,7 @@ sealed trait Schedule extends Loggable {
try {
f.apply()
} catch {
- case e: Exception => logger.error(e)
+ case e: Exception => logger.error(e.getMessage, e)
}
}
}
@@ -162,7 +162,7 @@ sealed trait Schedule extends Loggable {
Schedule.this.restart
pool.execute(r)
} catch {
- case e: Exception => logger.error(e)
+ case e: Exception => logger.error(e.getMessage, e)
}
}
}
What do you people think, whould you welcome a PR for this?
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963