I tried this already, but it doesn't seem to have any effect on logging...
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this
Ah, sorry it requires logger being set to debug mode too. Thanks !
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message
Samuel how did you manage to enable this logging :
[DEBUG] [04/30/2015 22:36:01.921] [default-akka.actor.default-dispatcher-8]
[akka://default/system/deadLetterListener] stopped [DEBUG] [04/30/2015
22:36:01.922] [default-akka.actor.default-dispatcher-5]
Probably via withDebug on the materializer settings, e.g.
ActorMaterializer(ActorMaterializerSettings(system).withDebugLogging(true))
On Thursday, July 16, 2015 at 11:28:28 AM UTC-5, Jakub Liska wrote:
Samuel how did you manage to enable this logging :
[DEBUG] [04/30/2015 22:36:01.921]
Hi,
If a stream is not stopped normally, but the system is shut down
underneath, then it sends an error message to all of its downstreams
(because it is not normal completion) so they can clean up properly. If you
see these messages during system shutdown then it means some streams were
still
Hi.
With akka http 1.0-RC2 (was similar in 1.0-RC1), one of my program signals
an intermittent error that I do not understand.
The context: one HTTP GET request is sent out, the JSON response is
properly received, decoded and acted upon, and then the system terminates
with (system being my
