EventJournal adapters sometimes are not registered about xoom-lattice

[bwehrle]

Based on our conversation regarding how entity state should be managed in actor and constructors, I'm going to change my implementation as I suspect that using the apply() in the entity constructor might be related to this problem.

[VaughnVernon]

@bwehrle Thanks! Would you mind attempting to debug this via vlingo-actors? It is possible that the following is involved:

0. Sourced::apply(???)
1. Actors::stowMessages()
2. Sourced::appendResultedIn()/appendAllResultedIn()
3. Actors::disperseStowedMessages()

It's possible that the stowed messages are being dispatched prematurely or out of order.

[VaughnVernon]

@bwehrle Would you please pull version 0.7.9 just released and let me know whether this Issue has been fixed? The binary artifacts are on Bintray only:

https://bintray.com/vlingo/vlingo-platform-java

  <repositories>
    <repository>
      <id>jcenter</id>
      <url>https://jcenter.bintray.com/</url>
    </repository>
  </repositories>

I think that the problem was with CompletesEventually pooled actors were being selected for various requests and could complete out of order, which would cause restore() and apply() to fail under some conditions. Now a given actor that requests a eventual completion should see each of the completions occur in the order in which they were requested. If this doesn't fix your issue then I will need a complete example that causes the issue.

[bwehrle]

Hi, I´m still seeing this issue, and it happened pretty quickly, after a few runs. I moved the vlingo pom dependencies to 0.7.9 in my fork for my example project.. I think if you pull the new code this should repo again for you quickly. I didn´t try this with the other examples, but I assume you can repo with them as well doing the same type of repetitive test run. Regards, Brian

…

On Mon, Jan 7, 2019 at 4:50 AM Vaughn Vernon ***@***.***> wrote: @bwehrle <https://github.com/bwehrle> Would you please pull version 0.7.9 just released and let me know whether this Issue has been fixed? The binary artifacts are *on Bintray only*: https://bintray.com/vlingo/vlingo-platform-java <repositories> <repository> <id>jcenter</id> <url>https://jcenter.bintray.com/</url> </repository> </repositories> I think that the problem was with CompletesEventually pooled actors were being selected for various requests and could complete out of order, which would cause restore() and apply() to fail under some conditions. Now a given actor that requests a eventual completion should see each of the completions occur in the order in which they were requested. If this doesn't fix your issue then I will need a complete example that causes the issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AOjeNGvXx6wktlLr7Q06L_QWuy7lDi8Yks5vAsPogaJpZM4ZooOi> .

[bwehrle]

I think this issue is resolved; after making the recommended changes I cannot get this to repo (I am hitting other different issues). So I will close this for now.