I don't think this is anything to worry about, but let us know if you find
anything that is not working as expected.
Regards,
Patrik
On Mon, Oct 20, 2014 at 6:59 PM, Richard Rodseth rrods...@gmail.com wrote:
Yes, I'm using 2.3.6. I *think* the result is still correct, but haven't
had time to
Thanks for sharing. Yes, -XX:+HeapDumpOnOutOfMemoryError is on the JVM
level, and the dump is taken when the OutOfMemoryError is thrown.
Documented here:
http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html
/Patrik
On Tue, Oct 21, 2014 at 4:39 PM, Sébastien Lorber
Hi,
I looked at your code. A few comments:
- What is the purpose of using ask in the Retry actor? The timeout failure,
and akka.actor.Status.Failure replies will be sent (pipeTo) to the original
sender anyway.
- Does it work? Is the message in preRestart defined when the child fails?
A new Retry
Thanks a lot!
/Patrik
On Tue, Oct 21, 2014 at 10:02 PM, Jeroen Gordijn jeroen.gord...@gmail.com
wrote:
I created a fix in this pull request:
https://github.com/akka/akka/pull/16117
Cheers
Jeroen
Op maandag 20 oktober 2014 18:09:59 UTC+2 schreef Patrik Nordwall:
Thanks!
On Mon, Oct 20,
Hi,
I'm converting an homegrown (cassandra based) persistence system to the
akka-persistence system.
My system have clients connecting to it, creating a session in the
system. This session is implemented as SessionActor (which is now a
PersistentActor using the session id as persistenceId) and
I think I would make the sessions persistent actors, children of a
SessionManager that is not a persistent actor. The SessionManager can
always see if a child exists.
http://typesafe.com/activator/template/akka-persistence-event-sourcing
I'm seeing the same entries in my log, but everything is working just fine.
I haven't looked into it yet, but I'm wondering what is the cause of this
message. There are a lot of these kind of logging entries in my log and
they appear on every startup of my app.
Cheers,
Jeroen
Op woensdag 22
If you have a use case that involves checking for session existence without
sending a command to the session, you could publish a SessionCreated
*domain* event (not an Akka persistence event) to the read side by
publishing it to an Akka EventBus. The subscriber could then store some
Hi,
On Wed, 2014-10-22 at 08:46 -0700, Richard Rodseth wrote:
If you have a use case that involves checking for session existence
without sending a command to the session, you could publish a
SessionCreated *domain* event (not an Akka persistence event) to the
read side by publishing it to
I'm hoping Typesafe will come up with a great solution. I noticed that
Scala Pickling is making its way into Spark
At the very end of this good talk, he mentions plans to use Pickling in
Spark.
http://functional.tv/post/9769999/scala-by-the-bay2014-matei-zaharia-next-generation-langu
and
Hello!
Here's my problem:
I have an Actor which is both an ActorSubscriber[A] and an
ActorPublisher[B](Processor?).
Since I want to embed the processor somewhere else, I would like to send
around a Flow[A,B] instead of
a Subscriber/Publisher pair and later on connecting them manually.
Can
I thought I read/heard somewhere that Pickling is aiming to become the
default serialization mechanism in Scala, but I cannot find any proof (like
a SIP) for it (yet).
Integrating Pickling in Spark is currently work in progress:
Team,
I working on a app built on top of akka persistence and java.
I am using cassandra plugin i.e. akka-persistence-cassandra_2.10-0.3.4.jar.
Its from repository http://dl.bintray.com/krasserm/maven/.
I am facing below exception. Kindly let me know, what is the expected fix.
Uncaught error
13 matches
Mail list logo
