Hi again, I'm still fighting with the integration of akka persistence into our tool, especially with our testsuite. The problem I have now is that everytime I run the whole testsuite on my machine, I keep getting java crashes caused by segmentation faults. When I open the bug report, here is the stacktrace:
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j org.fusesource.leveldbjni.internal.NativeIterator$IteratorJNI.delete(J)V+0 j org.fusesource.leveldbjni.internal.NativeIterator.delete()V+8 j org.fusesource.leveldbjni.internal.JniDBIterator.close()V+4 j akka.persistence.journal.leveldb.LeveldbStore$class.withIterator(Lakka/persistence/journal/leveldb/LeveldbStore;Lscala/Function1;)Ljava/lang/Object;+26 j akka.persistence.journal.leveldb.LeveldbJournal.withIterator(Lscala/Function1;)Ljava/lang/Object;+2 j akka.persistence.journal.leveldb.LeveldbRecovery$class.replayMessages(Lakka/persistence/journal/leveldb/LeveldbStore;IJJJLscala/Function1;)V+17 j akka.persistence.journal.leveldb.LeveldbJournal.replayMessages(IJJJLscala/Function1;)V+9 j akka.persistence.journal.leveldb.LeveldbRecovery$$anonfun$asyncReplayMessages$1.apply$mcV$sp()V+24 j akka.persistence.journal.leveldb.LeveldbRecovery$$anonfun$asyncReplayMessages$1.apply()V+1 j akka.persistence.journal.leveldb.LeveldbRecovery$$anonfun$asyncReplayMessages$1.apply()Ljava/lang/Object;+1 j scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1()Lscala/util/Try;+8 j scala.concurrent.impl.Future$PromiseCompletingRunnable.run()V+5 j akka.dispatch.TaskInvocation.run()V+4 j akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec()Z+4 J scala.concurrent.forkjoin.ForkJoinPool.runWorker(Lscala/concurrent/forkjoin/ForkJoinPool$WorkQueue;)V j scala.concurrent.forkjoin.ForkJoinWorkerThread.run()V+14 v ~StubRoutines::call_stub This seems to happen during shutdown of the actor system. We have around 200 tests, and for most of them we destroy the actor system after the test. So ActorSystems are being destroyed and created very often. Is this a problem? Also we do not explicitly stop the channels when the corresponding actors are shutdown, we will be trying that out today. The crash does not always occur, and when it does, it occurs in different tests, so I cannot really reproduce this. Another issue we have is that some of our tests seem to have timeout issues since we introduced akka persistence, sometimes they receive their messages before the timeout, sometimes they don't. This of course will then make other tests fail, as there are still unconfirmed messages hanging around. Timeouts are pretty low, to get our testsuite done as quick as possible, so running into timeout issues is not very surprising. Right now I am thinking about creating an in-memory journal for use in tests to make our tests more stable. That should solve a lot of the issues we see right now. Is this a valid approach in your eyes? Cheers, Michael -- >>>>>>>>>> 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.
