Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown flow operation in akka-http #158

Closed
akka-ci opened this issue Sep 8, 2016 · 1 comment
Closed

Unknown flow operation in akka-http #158

akka-ci opened this issue Sep 8, 2016 · 1 comment
Milestone

Comments

@akka-ci
Copy link

akka-ci commented Sep 8, 2016

Issue by acjay
Tuesday Mar 29, 2016 at 18:50 GMT
Originally opened as akka/akka#20176


When logging in debug mode using Akka-Http in Akka 2.4.2, I get mysterious debug log entries, apparently related to connection timeouts. The unknown-operation lines in particular are mysterious. I'm seeing this following a successful POST request to my application.

I'm wondering if it might be a good idea to have more granular control over logging in Akka-Http, similar to how the akka.actor.debug.* config entries allow the programmer to opt-in to greater levels of detail for regular Actors.

(mentioned to @ktoso on Gitter)

Example:

background log: info: [ERROR] [03/29/2016 14:29:25.268] [causality-akka.actor.default-dispatcher-18] [akka://causality/user/StreamSupervisor-0/flow-3-0-unknown-operation] Error in stage [recover]: No elements passed in the last 1 minute. (akka.http.impl.engine.HttpConnectionTimeoutException)
background log: info: [DEBUG] [03/29/2016 14:29:25.268] [causality-akka.actor.default-dispatcher-18] [akka://causality/user/StreamSupervisor-0/flow-3-0-unknown-operation] Aborting tcp connection because of upstream failure: No elements passed in the last 1 minute.
background log: info: akka.stream.impl.Timers$IdleTimeoutBidi$$anon$4.onTimer(Timers.scala:147)
background log: info: akka.stream.stage.TimerGraphStageLogic.akka$stream$stage$TimerGraphStageLogic$$onInternalTimer(GraphStage.scala:1125)
background log: info: akka.stream.stage.TimerGraphStageLogic$$anonfun$akka$stream$stage$TimerGraphStageLogic$$getTimerAsyncCallback$1.apply(GraphStage.scala:1114)
background log: info: akka.stream.stage.TimerGraphStageLogic$$anonfun$akka$stream$stage$TimerGraphStageLogic$$getTimerAsyncCallback$1.apply(GraphStage.scala:1114)
background log: info: akka.stream.impl.fusing.GraphInterpreter.runAsyncInput(GraphInterpreter.scala:564)
background log: info: akka.stream.impl.fusing.GraphInterpreterShell.receive(ActorGraphInterpreter.scala:397)
background log: info: akka.stream.impl.fusing.ActorGraphInterpreter$$anonfun$receive$1.applyOrElse(ActorGraphInterpreter.scala:547)
background log: info: akka.actor.Actor$class.aroundReceive(Actor.scala:480)
background log: info: akka.stream.impl.fusing.ActorGraphInterpreter.aroundReceive(ActorGraphInterpreter.scala:493)
background log: info: akka.actor.ActorCell.receiveMessage(ActorCell.scala:526)
background log: info: akka.actor.ActorCell.invoke(ActorCell.scala:495)
background log: info: akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)
background log: info: akka.dispatch.Mailbox.run(Mailbox.scala:224)
background log: info: akka.dispatch.Mailbox.exec(Mailbox.scala:234)
background log: info: scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
background log: info: scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
background log: info: scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
background log: info: scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
background log: info: [DEBUG] [03/29/2016 14:29:25.269] [causality-akka.actor.default-dispatcher-18] [akka://causality/user/StreamSupervisor-0/flow-3-0-unknown-operation] stopped
background log: info: [DEBUG] [03/29/2016 14:29:25.270] [causality-akka.actor.default-dispatcher-20] [akka://causality/system/IO-TCP/selectors/$a/2] no longer watched by Actor[akka://causality/user/StreamSupervisor-0/$$c#-816387569]
background log: info: [DEBUG] [03/29/2016 14:29:25.270] [causality-akka.actor.default-dispatcher-20] [akka://causality/system/IO-TCP/selectors/$a/2] stopped
background log: info: [DEBUG] [03/29/2016 14:29:25.270] [causality-akka.actor.default-dispatcher-19] [akka://causality/system/IO-TCP/selectors/$a] received AutoReceiveMessage Envelope(Terminated(Actor[akka://causality/system/IO-TCP/selectors/$a/2#1992616070]),Actor[akka://causality/system/IO-TCP/selectors/$a/2#1992616070])
@akka-ci
Copy link
Author

akka-ci commented Sep 8, 2016

Comment by drewhk
Wednesday Mar 30, 2016 at 08:54 GMT


The unknown-operation lines in particular are mysterious.

This means that the stream processing stage (the timeout handler in this case) was not given a name. I wonder why it has no explicit name here.

@akka-ci akka-ci added the t:http label Sep 8, 2016
@ktoso ktoso added this to the duplicate milestone Sep 8, 2016
@ktoso ktoso closed this as completed Sep 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants