Okay, cool -- glad to hear you found the issue...
On Thu, Jul 28, 2016 at 8:49 AM, Love Hasija
wrote:
> Thanks for your help Justin.
>
> I explored a little bit more on the Master worker and you were right. The
> problem was that for each ask i was keeping an actor instance level
> reference to
Thanks for your help Justin.
I explored a little bit more on the Master worker and you were right. The
problem was that for each ask i was keeping an actor instance level
reference to the caller, and that's the reason for each ask message, the
response was directing to a single actor reference,
Hmm. Nothing apparently wrong with that. You say that messages are
dropping into dead letters -- is that the requests or the responses that
are being dropped? If it's the responses, it might be helpful to see the
code of the master, which is likely to be the source of the problem...
On Wed, Jul
Yeah you are right. Actually that's what is happening. I may not have
explained it right.
The Actor system has a hierarchy of master and multiple workers. The master
is responsible for correlating the stream of result from the workers,
correlating, aggregating and returning a single response to
Hmm -- I think you may be misunderstanding ask. Ask sends *one* message,
and gets *one* response. It sounds like you're trying to use it to get a
stream of responses, and it just doesn't do that.
For that matter, ask gives you back a Future, and Future only returns a
single response. It's not d
Hi,
I am observing a strange behavior but I am sure, I did something wrong.
I have a service class providing a DB Wrapper, which has async methods for
providing services. Internally there is an actor workflow. but the service
class is not part of actor system and simply invokes ask to the actor