Re: [akka-user] Using Scheduler vs deadline to mimic some backend: scheduler is slow(er)

Hi Alex, On Mon, Sep 15, 2014 at 9:10 AM, Alex Wouda awo...@gmail.com wrote: Hi, Thanks for the reply. Ok, I have been misinformed. My perception was that actually calling Thread.sleep is a no-go and blocks the Thread for other actors. But using the Duration Deadline is indeed hogging up

Re: [akka-user] Per-request actor trait

Hi Richard, you can use type parameters in the case classes and in the creator methods. trait PerRequest[Request] extends Actor { ... } object PerRequest { case class WithActorRef[Request](r: RequestContext,target: ActorRef,message: Request) extends PerRequest[Request] } trait

Re: [akka-user] Using Scheduler vs deadline to mimic some backend: scheduler is slow(er)

Hi Patrick, Thanks for the explanation. On Monday, September 15, 2014 10:53:30 AM UTC+2, Patrik Nordwall wrote: Hi Alex, On Mon, Sep 15, 2014 at 9:10 AM, Alex Wouda awo...@gmail.com javascript: wrote: Hi, Thanks for the reply. Ok, I have been misinformed. My perception was that

Re: [akka-user] Using Scheduler vs deadline to mimic some backend: scheduler is slow(er)

On Mon, Sep 15, 2014 at 11:05 AM, Alex Wouda awo...@gmail.com wrote: Hi Patrick, Thanks for the explanation. On Monday, September 15, 2014 10:53:30 AM UTC+2, Patrik Nordwall wrote: Hi Alex, On Mon, Sep 15, 2014 at 9:10 AM, Alex Wouda awo...@gmail.com wrote: Hi, Thanks for the reply.

Re: [akka-user] Using Scheduler vs deadline to mimic some backend: scheduler is slow(er)

ok, clear. Thanks guys for the explanations. We'll use Scheduler for future stub backends. Alex On Monday, September 15, 2014 11:29:57 AM UTC+2, drewhk wrote: kes aprox 60ms and using the scheduler we saw that it was 80ms we tried the deadline. Scheduler is not optimized for high

[akka-user] single-sender/many-destination solution

Hi all Is it possible to implement single sender/many destination solution with at-least-once delivery based on AtLeastOnceDelivery trait I'll be much appreciated for links, exampless, references Regards Haghard -- Read the docs: http://akka.io/docs/ Check the FAQ:

Re: [akka-user] Cluster Sharding and akka-persistence-jdbc. Snapshots fail because snapshotSequenceNr isn't incrementing.

Hi Dennis, On Fri, Sep 12, 2014 at 9:57 PM, Dennis Vriend dnvri...@gmail.com wrote: Hi, akka-persistence-testkit has no test for this case, it's an Akka cluster issue as far as I can tell. Most use cases create snapshots based upon some kind of counter variable every 100 of journal entries

Re: [akka-user] Getting java.io.InvalidClassException (no valid constructor) with case objects

Hi, I had similiar problem with case classes which also derive from an abstract one. Did you get around it? tnks. Rod On Tuesday, December 11, 2012 10:58:33 AM UTC, rkuhn wrote: Hi, case objects are still objects (i.e. not static), so they will be serialized. Are you sure that

Re: [akka-user] Getting java.io.InvalidClassException (no valid constructor) with case objects

Tried making StateCategory extends Serializable? On Mon, Sep 15, 2014 at 2:43 PM, Rodrigo Boavida rodrigo.boav...@gmail.com wrote: Hi, I had similiar problem with case classes which also derive from an abstract one. Did you get around it? tnks. Rod On Tuesday, December 11, 2012 10:58:33

Re: [akka-user] Connecting DistributedPubSubMediators between different ActorSystems

Tnks for the reply Patrik. Yes we have that option on the table as well, but would each node in the cluster still participate in the gossip control of all the other nodes, or would it be confined to nodes within the same role? Let me expand a bit on what we have. Both backend and front end

Re: [akka-user] akka as MQs

thank you Martynas, I wrote a sample, and two unclear points for me on deleteMessages( toSeqId ). 1) How should application logically/priodically delete messages in a high load environment? Can't we hook into confirmDelivery method so that every confirmed message gets deleted? 2) Can default

[akka-user] Akka actors monitoring

Hi, I'm new to Akka actors, and used to work with Resque and Jesque for workers implementation. There's something missing in akka actors, is the administration tool, allowing us to monitor actors and their state, work load and the message in their mailbox. Is there a took that offers these

Re: [akka-user] single-sender/many-destination solution

Hi Haghard, On Mon, Sep 15, 2014 at 11:54 AM, Vadim Bondarev haghar...@gmail.com wrote: Hi all Is it possible to implement single sender/many destination solution with at-least-once delivery based on AtLeastOnceDelivery trait I assume that you imply that the sender doesn't know of the

Re: [akka-user] single-sender/many-destination solution

Thank you very much Patrik for your answer понедельник, 15 сентября 2014 г., 18:18:37 UTC+4 пользователь Patrik Nordwall написал: Hi Haghard, On Mon, Sep 15, 2014 at 11:54 AM, Vadim Bondarev hagh...@gmail.com javascript: wrote: Hi all Is it possible to implement single sender/many

Re: [akka-user] Per-request actor trait

Thanks. I'll play around with that, but I think we need RequestType and ResultType. With Spray becoming part of Akka, it might be nice to have the building blocks for per-request actors included? On Mon, Sep 15, 2014 at 1:58 AM, Martynas Mickevičius martynas.mickevic...@typesafe.com wrote: Hi