As a follow-up to this, the problem was of course of my own creation. However,
what wasn’t obvious to me was that the default behaviour of an InHandler is to
complete the stage once the upstream is completed. The API doc states:
Called when the input port is finished. After this callback no other
callbacks will be called for this port.
…but what it fails to state is that the default behaviour is to complete the
stage. Same goes for the OutHandler when the downstream is complete (which
makes more sense to me as default behaviour).
The reason that this became an issue for me was because my upstream completed
very quickly (it was a Source.single). Thus, my custom stage completed fast and
my async handler fired, but didn’t get processed.
Would a PR be welcomed to enhance the API doc for InHandler and OutHandler? I
think it’d be good to mention that completeStage is called by default and that
any outstanding async requests will go unprocessed.
Cheers,
-C
--
>>>>>>>>>> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
