On 16.03.14 13:14, Raymond Roestenburg wrote:
Ok you can also ignore this one,

(this is a fantastic rubber ducking session by the way! ;-P)

When I create the channel outside of the processor and reuse that, everything works as expected:

https://gist.github.com/RayRoestenburg/9582319

Of course every new child channel cannot know which messages were delivered earlier. Duh.

You should be able to use a child channel. Just make sure that the channel has the same id across incarnations. It is recommended to pass a channel id via Channel.props (more details at channel identifiers <http://doc.akka.io/docs/akka/2.3.0/scala/persistence.html#id9>).


On Sunday, March 16, 2014 12:42:27 PM UTC+1, Raymond Roestenburg wrote:

    Ok, I've got another question.. I've expanded the gist:

    https://gist.github.com/RayRoestenburg/9581923
    <https://gist.github.com/RayRoestenburg/9581923>

    I've added a channel to respond to clients to the NumberProcessor
    example, (NumberProcessorWithChannel) and I see something
    unexpected again, which might be me learning how this really
    works, or a bug?

    When a processor with the same name is started, I see replayed
    messages going to the probe which I have previously confirmed.
    Is that correct behavior? I would have expected that confirmed
    messages are not sent back to clients.

    On Sunday, March 16, 2014 12:01:59 PM UTC+1, Raymond Roestenburg
    wrote:

        Please disregard, I misunderstood and found out why.

        The replayed message causes the response back to the probe.

        On Sunday, March 16, 2014 10:17:08 AM UTC+1, Raymond
        Roestenburg wrote:

            Hi guys,

            I'm writing up some examples for persistence and stumbled
            on a strange issue.
            Can you please have a look at this? The gist contains a
            unit test you can drop straight into akka-persistence to
            verify it.

            https://gist.github.com/RayRoestenburg/9580479
            <https://gist.github.com/RayRoestenburg/9580479>

            I used to use ImplicitSender in the test, and found out
            that using two probes actually made the test pass,
            something I think should not be necessary.

            (There is always the chance that I totally misunderstand
            or made an incorrect assumption, but I think this is a bug)

            Cheers,
            Ray

--
>>>>>>>>>> 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] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

--
Martin Krasser

blog:    http://krasserm.blogspot.com
code:    http://github.com/krasserm
twitter: http://twitter.com/mrt1nz

--
     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 http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to