Re: [akka-user] Akka Persistence With Java and Cassandra Plugin Throwing Exception

Hey Martin, Let me check. I will validate this, missed to check this version. -Prakhyat m m Sent from my iPhone > On 24-Oct-2014, at 0:37, Martin Jöhren wrote: > > You say that you are using scala 2.11 but the library that you are using is > for 2.10. Can you double check? > > --

[akka-user] Re: Akka version conflict with Spark and Play

"shaded" part in the qualifier most probably comes from here http://maven.apache.org/plugins/maven-shade-plugin/ My speculation would be that Spark folks folded protobuf classes in to their home-cooked akka-actor jar to avoid version conflict between protobuf version used by Akka and the version

[akka-user] Akka version conflict with Spark and Play

Hello, I get an obscure runtime error with Spark if and only if there is another Akka JAR in the classpath. Unfortunately, I want to use Spark and Play in the same project, and SBT pulls in: akka-actor_2.10-2.3.4.jar for Play 2.3.4 akka-actor_2.10-2.2.3-shaded-protobuf.jar for Spark

[akka-user] Re: Event versioning revisited

We are using MessagePack as our binary serialization format. It works quite well. To support versioning(when later needed) of our serialized events(or any other data) we use a custom serializer. It's not nice and not fast(never benchmarked it), but for us it was important to be able to seriali

[akka-user] Re: [akka-stream 0.9] Create Flow[A,B] from Publisher[A] and Subscriber[B]

Hi Patrick, We have the following use case: Our application is a CQRS System that currently uses akka stream from the input(Commands) via command processors to the resulting event stream. We have two read sides: - One that simply consumes events and creates views from the events. This one is

Re: [akka-user] Akka Persistence With Java and Cassandra Plugin Throwing Exception

You say that you are using scala 2.11 but the library that you are using is for 2.10. Can you double check? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archi

Re: [akka-user] Event versioning revisited

It is, but it still has some rough edges and is WIP. I would recommend against using it in production right now. You probably need to give it a couple more months. On Wednesday, October 22, 2014 2:17:19 AM UTC+2, rrodseth wrote: > > Thanks for the input. I wonder if anyone has tried Scala Pickli

Re: [akka-user] Akka Persistence With Java and Cassandra Plugin Throwing Exception

Hi Patrik, I too felt it can be because of classpath. But I verified all settings are done and working. We are using java 1.7 and it is defined in classpath. Also scala version used is 2.11 which is also defined in classpath. Let me know is there any other classpath settings required? Or any spe

[akka-user] Query strategies for akka-persistence

Hello fellow hakkers, we're developing a proof-of-concept application to evaluate akka and akka-persistence, and we've stumbled upon a maze of twisty little passages, all alike. ;) We've got the command/storage side of the CQRS paradigm implemented, nicely sharded with akka-cluster, and are now

Re: [akka-user] Akka Persistence With Java and Cassandra Plugin Throwing Exception

I would guess you have an invalid or incomplete classpath. /Patrik On Wed, Oct 22, 2014 at 9:28 PM, Prakhyat Mallikarjun wrote: > 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 rep

Re: [akka-user] [akka-stream 0.9] Create Flow[A,B] from Publisher[A] and Subscriber[B]

Hi Christian, That is not possible, at the moment. We need something similar for stream based TCP, see discussion here: https://github.com/akka/akka/issues/16071 ActorSubscriber and ActorPublisher was originally not designed for this usage as a Processor. Is there a specific reason that you can't

Re: [akka-user] How to tell if a given persistent actor ever persisted something?

Hi Brice, Sounds like you have found your way forward. A few curious thoughts. Are you using an Akka Cluster? Then Cluster Sharding might help you here. It would take the role of your SessionService and manages the session actors for you wit

Re: [akka-user] Resolve of unknown path to dead letters in Akka Persistence test

I think it is related to the stored sender ref. In many (but not all) cases that ref is invalid and restore fails during replay. Question is if we need to store the sender any more? Is it expected that the original sender is restored in receiveRecover? /Patrik On Wed, Oct 22, 2014 at 5:21 PM, Jer

Re: [akka-user] TestKit and ActorSelection

I'm not sure I understand what you are looking for. You can use the testActor (or the ref of a TestProbe) as sender for an ActorSelection. Then you can use the ordinary testkit methods to verify the replies. Please elaborate. Regards, Patrik On Wed, Oct 22, 2014 at 3:48 AM, Eugene Dzhurinsky

Re: [akka-user] actor migration issue

Hi, On Tue, Oct 21, 2014 at 5:38 PM, 汤雪华 wrote: > I have a question about actor when it is in the cluster environment. > Suppose we have four machines in the cluster now. And each machine have > many alive actors. > But now, we added a new machine into the cluster, so some message will be > hand

Re: [akka-user] TypedActor with 3 instances

Then you have to use one-way message sends, i.e. void methods. With UntypedActor you can do this, also with ask (returning Future). Regards, Patrik On Tue, Oct 21, 2014 at 2:27 PM, Kostas kougios < kostas.koug...@googlemail.com> wrote: > Say I got 3 jvms, A , B and C. A is calling a method on a

Re: [akka-user] dead letters encountered and timed out replies

>> If I am not able to filter out this kind of errors from the dead-letter >> log, it is useless to look at it. > > Dead letters are useful to look at then you send things to wrong / dead > actors and you didn't notice for example. yes, in fact it is potentially very useful and I would like to che