This document
<http://doc.akka.io/docs/akka-http/10.0.5/scala/http/low-level-server-side-api.html#connection-failures>
describes
how to capture a connection failure that is caused by the client.
However, I found that the recovery clause of reactToConnectionFailure is
never executed.
I tested by replacing
.map { request =>
// simple streaming (!) "echo" response:
HttpResponse(entity = HttpEntity(ContentTypes.`text/plain(UTF-8)`,
request.entity.dataBytes))
}
with
.mapAsync(1) { request =>
*Future.never*
}
so I have time to break the connection from the client side.
Akka logging indicates
> [DEBUG] [05/02/2017 13:04:33.645]
> [default-akka.actor.default-dispatcher-6]
> [akka://default/system/IO-TCP/selectors/$a/3] Closing connection due to IO
> error java.io.IOException: An established connection was aborted by the
> software in your host machine
The .log() operation simply indicates that "Upstream finished".
--
>>>>>>>>>> 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 because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
