t; --
>
> *Heiko Seeberger*
> Home: heikoseeberger.de
> Twitter: @hseeberger <https://twitter.com/hseeberger>
> Public key: keybase.io/hseeberger
>
> On 15 Nov 2015, at 14:33, Alex Wouda >
> wrote:
>
> Hi,
>
> I'm trying to get a simple app running in do
Hi,
I'm trying to get a simple app running in docker, this works. But then I'm
not able to access the remote akka system from the host.
Using scala 2.11.7 and Akka 2.4.0
Whole project is available here: https://github.com/awouda/akka-docker.git
My 'server system' configuration:
akka {
ac
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
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 > wrote:
>
>> Hi,
>>
>> Thanks for the reply.
>> Ok, I have been misinforme
Hi,
We have an ' aggregation' actor in place. We do not use the Aggregator
pattern. But a have a parent actor that knows how many responses should be
received.
For example the code looks simplified like this:
class CoreFlowActor extends Actor {
val workers = List(WorkerActorA, WorkerActor
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 CPU cycles but not blocking the
thread.
The idea was to mimic some work that norma
Hi,
We have a system where we in some cases mimic our backed services by just
creating some 'wait time'.
This to prove our own overhead is very low.
My colleague and I differ on the approach of the 'wait time'. I decided to
use the dealine approach as I used in the akka course (mimics the acto
We discussed that we're actually testing the akka-framework when we want to
achieve this. So we skip this.
regards,
Alex
On Tuesday, January 14, 2014 4:21:34 PM UTC+1, Alex Wouda wrote:
>
> Hi,
>
> We have an actor with child actors. Those 3 register themselves in the
Hi,
We have an actor with child actors. Those 3 register themselves in the
preStart on the eventstream, and deregegister themselves in the postStop.
The 3 child actors are just referenced/instantiated in the prestart of the
parent by means of context.actorOf( etc.).
Now we want to test when th
