-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistence: persist() does not stash when invoked while handling RecoveryCompleted #21736
Labels
Milestone
Comments
Workaround: Put the check inside |
ortibazar
pushed a commit
to ortibazar/akka
that referenced
this issue
Nov 24, 2016
ortibazar
pushed a commit
to ortibazar/akka
that referenced
this issue
Nov 28, 2016
ortibazar
pushed a commit
to ortibazar/akka
that referenced
this issue
Dec 13, 2016
ktoso
pushed a commit
that referenced
this issue
Dec 14, 2016
Not backporting, it's not critical to have this back in 2.4 I think |
patriknw
pushed a commit
that referenced
this issue
Feb 21, 2017
I have backported it, because something else was depending on it |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I have a
PersistentActor
that wants to self-initialize like such:However, incoming commands aren't stashed between persisting the
createInitialEvent()
and getting the callback toupdateSomeState()
(which does happen eventually, I think as the next command is handled).In
EventSourcing.scala
, the reason is that the detecting ofpendingStashingPersistInvocations
isn't performed until the state reachesprocessingCommands
. Perhaps a well-placedchangeState(persistingEvents)
insiderecoveryStarted(...)
orrecovering(...)
could make it work.Otherwise, blow up if
persist()
is invoked during receiveRecover.The text was updated successfully, but these errors were encountered: