Hi,
Today I dumped the communication and it looks that we pass the
akka.remote.secure-cookie in plain-text over the wire. My look at
AkkaProtocolTransport.scala confirmed that. I understand that this is not
supposed to be strong authentication but still it is pretty weak one.
This is
Hi all,
I have configured a logLevel of INFO in my application.conf:
akka {
loglevel = INFO
}
Nevertheless when running the tests (with sbt) I see messages of
debug-Level, eg:
[DEBUG] [01/28/2014 15:02:13.493] [ScalaTest-run]
[EventStream(akka://EvaluatorSpec)] logger
Is Bar — router?
понедельник, 27 января 2014 г., 23:16:46 UTC-5 пользователь Oleg
Zhurakousky написал:
Actually i think you are missing one more ../. I just built a hierarchy
that looks like yours and it works just fine:
//akka/user
| \
Jane John
|
Foo
|
Bar
|
Baz
Well, now it is and I see what your problem is.
When dealing with router Akka will create routees based on the routing
strategy you select, so in my case I chose RoundRobin:
val bar =
context.actorOf(Props[Bar].withRouter(RoundRobinRouter(nrOfInstances = 5)))
So what ends up happening is Aka
hi guys!
I was trying to configure the gossip interval here :
contrib.cluster.pub-sub {
# Actor name of the mediator actor, /user/FumigoPubSubMediator
name = FumigoPubSubMediator
# Start the mediator on members tagged with this role.
# All members are used if
Hi,
I ran into this problem: when preStart is overriden (empty) for an FSM
actor it stops sending CurrentState in response
to SubscribeTransitionCallBack. Tried putting
startWith
initialize
into preStart, still not getting CurrentState. What is the correct solution
in this case? I am
Can you share some code. I just tried to reproduce it based on your
explanation and it all works for me (see code below), but may be I am
missing something.
Cheers
Oleg
=
import akka.actor.Actor
import akka.actor.ActorSystem
import akka.actor.FSM
import
Thanks, Oleg,
If you make FsmActor in your example inherit from Processor (from
akka-persistence) you'll see the effect
(class FsmActor extends Processor with FSM[State, Data] {)
Vadim
--
Read the docs: http://akka.io/docs/
Check the FAQ: http://akka.io/faq/
Search the
This is a good example of why such a lookup is not as good an idea as it seems
at first: your hierarchy is now pretty much fixed, your actors start failing if
you change some details about their parents. A much more robust solution is to
not use actorSelection and instead just pass John’s
I know, that if I use a consistent hashing group router, it will always
rout to the same registered routees.
So I wrote my application, with a few routees on there own routee-nodes and
a public-node with a router, which is reachable by the client.
If the client sends a message it is routed
Using Processor actor implies that there may be some initial state, so its
preStart() method sends a Recover message to facilitate the recovery before
anything else happens.
The important part is that until the Recovery message is received by
Processor everything else sent to the Processor actor
On 29.01.14 03:53, Oleg Zhurakousky wrote:
Using Processor actor implies that there may be some initial state, so
its preStart() method sends a Recover message to facilitate the
recovery before anything else happens.
The important part is that until the Recovery message is received by
12 matches
Mail list logo
