akka-persistence

akka persistence, resume on failure, at least once semantics

由 核能气质少年 提交于 2019-12-08 04:07:18
问题 I have small mess in my head Avoid having poisoned mailbox http://doc.akka.io/docs/akka/2.4.2/general/supervision.html The new actor then resumes processing its mailbox, meaning that the restart is not visible outside of the actor itself with the notable exception that the message during which the failure occurred is not re-processed. My case: actor receives the "command" to run smth. Actor tries to reach remote service. Service is unavailable. Exception is thrown. I want actor to keep going

Why doesn't the Akka Persisence Query Read Journal retrieve my events?

由 本小妞迷上赌 提交于 2019-12-08 01:01:34
问题 I have problems understanding Akka Persistence Query, especially the method eventsByTag since it doesn't behave like I expect. In my main class I call a class that starts listening to any events being persisted with a certain tag. class CassandraJournal(implicit val system: ActorSystem) { def engageStreaming = { val readJournal = PersistenceQuery(system).readJournalFor[CassandraReadJournal](CassandraReadJournal.Identifier) implicit val mat = ActorMaterializer() readJournal.eventsByTag(

Column family ID mismatch (found cebcc380-72d4-11e7-9a6b-bd620b945799; expected c05d6970-72d4-11e7-9a6b-bd620b945799)

由 久未见 提交于 2019-12-07 19:39:20
问题 How can i resolve this error Column family ID mismatch (found cebcc380-72d4-11e7-9a6b-bd620b945799; expected c05d6970-72d4-11e7-9a6b-bd620b945799) Caused by: java.util.concurrent.ExecutionException: org.apache.cassandra.exceptions.ConfigurationException: Column family ID mismatch (found cebcc380-72d4-11e7-9a6b-bd620b945799; expected c05d6970-72d4-11e7-9a6b-bd620b945799) at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[na:1.8.0_131] at java.util.concurrent.FutureTask.get

Why doesn't the Akka Persisence Query Read Journal retrieve my events?

由 那年仲夏 提交于 2019-12-06 12:07:15
I have problems understanding Akka Persistence Query, especially the method eventsByTag since it doesn't behave like I expect. In my main class I call a class that starts listening to any events being persisted with a certain tag. class CassandraJournal(implicit val system: ActorSystem) { def engageStreaming = { val readJournal = PersistenceQuery(system).readJournalFor[CassandraReadJournal](CassandraReadJournal.Identifier) implicit val mat = ActorMaterializer() readJournal.eventsByTag("account", Offset.noOffset) .runForeach { event => println(event) } } } Whenever I start my server and my

Column family ID mismatch (found cebcc380-72d4-11e7-9a6b-bd620b945799; expected c05d6970-72d4-11e7-9a6b-bd620b945799)

由 Deadly 提交于 2019-12-06 07:34:27
How can i resolve this error Column family ID mismatch (found cebcc380-72d4-11e7-9a6b-bd620b945799; expected c05d6970-72d4-11e7-9a6b-bd620b945799) Caused by: java.util.concurrent.ExecutionException: org.apache.cassandra.exceptions.ConfigurationException: Column family ID mismatch (found cebcc380-72d4-11e7-9a6b-bd620b945799; expected c05d6970-72d4-11e7-9a6b-bd620b945799) at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[na:1.8.0_131] at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[na:1.8.0_131] at org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java

Akka Persistence Cassandra with Akka 2.3.0 throwing fatal EOFException when used with Play 2.2.1

由 风格不统一 提交于 2019-12-06 05:31:38
问题 Any idea why I am getting the following error after adding Akka to my library dependencies and executing the test task? Uncaught error from thread [reactivemongo-akka.actor.default-dispatcher-4] shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[reactivemongo] akka.actor.ActorCell.create(ActorCell.scala:580) at akka.actor.ActorCell.invokeAll$1(ActorCell.scala:456) at akka.actor.ActorCell.systemInvoke(ActorCell.scala:478) at akka.dispatch.Mailbox

Akka Persistence Cassandra with Akka 2.3.0 throwing fatal EOFException when used with Play 2.2.1

由 末鹿安然 提交于 2019-12-04 12:12:47
Any idea why I am getting the following error after adding Akka to my library dependencies and executing the test task? Uncaught error from thread [reactivemongo-akka.actor.default-dispatcher-4] shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[reactivemongo] akka.actor.ActorCell.create(ActorCell.scala:580) at akka.actor.ActorCell.invokeAll$1(ActorCell.scala:456) at akka.actor.ActorCell.systemInvoke(ActorCell.scala:478) at akka.dispatch.Mailbox.processAllSystemMessages(Mailbox.scala:263) at akka.dispatch.Mailbox.run(Mailbox.scala:219) at akka.dispatch

How to approach the Q in CQRS when doing Event Sourcing with Akka?

由 杀马特。学长 韩版系。学妹 提交于 2019-12-03 21:19:53
问题 Is there a good way of doing CQRS when combined with Event Sourcing? One way I thought about was doing this in the Command handler (of a Persistent Actor) as soon as the Command was turned into an Event and persisted to the event log (these Events represent the Write model), I would send the event using the event bus to interested subscribing query actors so they can update their Query model. The other way I was thinking (provided the journal supports it) is to use persistence queries (via

Akka Persistence Query event stream and CQRS

由 匆匆过客 提交于 2019-11-29 09:46:38
问题 I'm trying to implement read side in my ES-CQRS architecture. Let's say I have a persistent actor like this: object UserWrite { sealed trait UserEvent sealed trait State case object Uninitialized extends State case class User(username: String, password: String) extends State case class AddUser(user: User) case class UserAdded(user: User) extends UserEvent case class UserEvents(userEvents: Source[(Long, UserEvent), NotUsed]) case class UsersStream(fromSeqNo: Long) case object GetCurrentUser

How to run Play 2.2.x with Akka 2.3.x?

由 空扰寡人 提交于 2019-11-29 09:25:35
Is there any way to combine akka 2.3 and play 2.2? For now I'm getting AbstractMethodError while running such application. I need to have them both in one app because Akka 2.3 comes with very useful akka persistence module which is very reliable(in opposition to it's predecessor) and such reliability is really important in my case. I've tried compiling play 2.2.2 from sources and changing akka dependency there to 2.3 but i still get the same error: [ERROR] [04/01/2014 09:42:26.105] [play-akka.actor.default-dispatcher-6] [ActorSystem(play)] Uncaught error from thread [play-akka.actor.default
订阅 akka-persistence