hmm, could you try adding the public-hostname = "127.0.0.1" to the helios.tcp segment
_
slc
@slc
will do now...
Ralf
@Ralf1108
hi all, I checked out the new Akka.net Streams feature and I think its very goog. One questions was left open. If I create a processing flow how can I distribute it across different machines. Are there any examples how to start?
Arjen Smits
@Danthar
not sure if its still needed.
slc
@slc
public-hostname = "127.0.0.1" Added. No change. Still errors.
do I need to configure IIS Express in any special way?
The weird thing is that I can send the message from the web actor to the service actor with no problems
Marc Piechura
@marcpiechura
@Ralf1108 that's not possible out of the box. But what you can do is to have an actor that distributes "job" messages to different machines and have a stream on every machine.
Arjen Smits
@Danthar
@slc no.
slc
@slc
I just cant Tell() back to the web actor from the service actor
James Farrer
@jamesfarrer
thanks @cgstevens and @qwoz . most helpful
Arjen Smits
@Danthar
@slc what if you reduce it to its bare minimum. So send a message containing nothing more then a string, and use Sender.Tell to echo it back
slc
@slc
I think I'm going to have to
Arjen Smits
@Danthar
that would eliminate possible serialization issues
I will try sending a string instead, or perhaps a bool
Ricky Blankenaufulland
@ZoolWay
@slc I have not followed the whole conversation but because I falled into the trap this week when messages have been swallowed: You are not creating one of the actors in an async method?
slc
@slc
nope, all syncronous
Ricky Blankenaufulland
@ZoolWay
ok
then check for the string/bool
slc
@slc
no async/await anywhere
yup, just about to try that
cannot Tell(true) either
:(
I guess that somewhat rules out serialisation/deserialisation issues
Im going to pull out an example from my solution and see if I can replicate in isolation