I have been trying to set the dispatcher for an actor system to be used by
default for actors created with the actor system but I can't get it to
work. Specifically, I want to use the
akka.testkit.CallingThreadDispatcher. I have tried the following two
configurations (at the classpath root)
default-dispatcher goes underneath akka.actor, not underneath akka.
Heiko
On Wed, May 14, 2014 at 8:32 AM, PVillela pvill...@gmail.com wrote:
I have been trying to set the dispatcher for an actor system to be used by
default for actors created with the actor system but I can't get it to
I don't think that this is a bug, it was designed that way, but it might be
unwanted behavior. The ActorSelection will try to traverse the path that you
give it, and send messages to all matching sub paths. The ActorSelection
doesn't know that it's ok to not find something at the end of the
Hi Luis,
Glad that it clarified some things at least ;)
Looking forward to hear about your use-case.
B/
On 13 May 2014 at 18:35:20, Luis Medina (lu4...@gmail.com) wrote:
Hi Björn,
Thank you for taking the time to answer my questions. It helped clarify some
things. I don't have a specific
In my usecase I don't hold a direct reference to the actorrefs, as they
happen to be child actors under their respective parent actors. Of course
you could argue that I should have sent message to the parent actors and
let them propagate the messages to the relevant child actors, to respect my
Hi,
I don't follow your question. The number of channels and actors are only
limited by your systems resources (Memory and Storage).
What are you trying to achieve? What is it that you want to shut down?
B/
On 13 May 2014 at 19:20:32, 何品 (hepin1...@gmail.com) wrote:
I ,If I want to deliver a
yes.
I want some method like get(seqNr) to get an message ,could that be done?
now,I need to save them in a Map
在 2014年5月14日星期三UTC+8下午6时29分27秒，Björn Antonsson写道：
Hi,
I'm not sure that I understand what you are trying to achieve. The
Persistent messages that you send to an Processor, or in
Hi Luis,
Receiving and sending 5000 messages per second should not be a problem.
Hopefully the storing and processing of those messages will keep up.
The EventBus is actor system local. It doesn't work over remoting. If you only
have a fixed number of consumers, I would go with a
Hi,
Just noticed project
Orleanshttp://research.microsoft.com/en-us/projects/orleans/,
which is like an actors implementation for .NET, still in preview I think.
It’s supposed to be higher-level than Akka, the description being:
It is actor-based, but differs from existing actor-based platforms
Hi Leon,
Have you looked at the paper for the TrieMap? It has some performance
comparisons with ConcurrentHashMap and ConcurrentSkipListMap.
Concurrent Tries with Efficient Non-Blocking Snapshots
B/
On 14 May 2014 at 07:05:42, Leon Ma (tutuf...@gmail.com) wrote:
Hi,
Any suggestions on how
Hi Leon,
The scheduler in Akka is based on a revolving wheel of time slots with lists of
timeouts in each slot. There is no limit on the number of entries.
B/
On 14 May 2014 at 07:44:55, Leon Ma (tutuf...@gmail.com) wrote:
I would do below in my code:
Hi,
You are right that you shouldn't use the journal as a database. If you want to
use event sourcing to model the changes on the client, then I would use a View
to populate a query model (maybe in a SQL database) that fits your queries.
B/
On 14 May 2014 at 13:15:51, 何品 (hepin1...@gmail.com)
I think just cause some guys using leveldb as as some redis thing ,and akka
persistence are using it default.
now I am going to store the information in some other place,redis for now.
thanks
在 2014年5月14日星期三UTC+8下午8时39分42秒，Björn Antonsson写道：
Hi,
You are right that you shouldn't use the
14 maj 2014 kl. 14:24 skrev Martijn Hoekstra martijnhoeks...@gmail.com:
On Wed, May 14, 2014 at 1:13 PM, Alexandru Nedelcu a...@bionicspirit.com
wrote:
Hi,
Just noticed project Orleans, which is like an actors implementation for
.NET, still in preview I think. It’s supposed to be
Thanks for pointing out! I'll have a look.
在 2014年5月14日星期三UTC+8下午7时52分14秒，Björn Antonsson写道：
Hi Leon,
Have you looked at the paper for the TrieMap? It has some performance
comparisons with ConcurrentHashMap and ConcurrentSkipListMap.
Concurrent Tries with Efficient Non-Blocking
Yes if you continually submit more tasks than you process (e.g. by submitting
them far into the future) then your JVM would eventually run out of memory, but
no rejections.
B/
On 14 May 2014 at 15:33:02, Leon Ma (tutuf...@gmail.com) wrote:
So, if I submit tasks very frequent and the task get
Thanks. That did the trick.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google
Hi Leon,
14 maj 2014 kl. 15:27 skrev Leon Ma tutuf...@gmail.com:
Thanks for the reply!
btw, regarding to mixing trait, I happened to have a quick question: (which
is actually a scala question rather than akka)
can I do dynamic mixing with some reflection utils like:
def
Ketil Bjorn,
If you look at the second post in this thread from Viktor, it seems his
recommendation is the opposite.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
Oh, I didn't realize the EventBus was local to the actor system, must have
missed it in the documentation. Thank you for pointing that out and thank
you for the suggestion. Can't wait for Akka-streams to be released!
--
Read the docs: http://akka.io/docs/
Check the FAQ:
You can delete messages from the journal or use an EventSourcedProcessor
which only stores/replays validated commands (messages).
Heiko
On Wed, May 14, 2014 at 10:21 PM, Lawrence Wagerfield
lawre...@dmz.wagerfield.com wrote:
Akka documentation highlights that actor state is reset on
Hello!
I'm trying to start 2 nodes in a cluster - one with role http and another
one with role chunk role. Initially there are no actors running at the
http node (ones should be deployed when node chunk joins the cluster)
my application.conf:
akka {
actor {
provider =
On May 14, 2014, at 2:32 PM, Björn Antonsson bjorn.antons...@typesafe.com
wrote:
Hi Daniel,
I'm not sure where your logic would be used. Are you using transient Channels
and a Processor or are you using PersistentChannels? If you are using a
PersistentChannel then you could limit the
Actors are thread safe inside them by definition.
The actor has one mailbox and processes the messages one by one from it.
We guarantee that fields are properly visible, even if the actor jumps
around threads - no need for CHM in the actor
On Thu, May 15, 2014 at 7:31 AM, Leon Ma
By processes the messages one by one, do you mean My message B has to be
wait until message A gets processed?
They can't be executed in parallel?
Thanks
Leon
在 2014年5月14日星期三UTC-7下午10时34分45秒，Konrad Malawski写道：
Actors are thread safe inside them by definition.
The actor has one mailbox and
No. This is inherent to how the actor model is defined. Thanks to this
youre safe from races inside the actor.
--
Konrad 'ktoso' Malawski
On 15 May 2014 07:43, Leon Ma tutuf...@gmail.com wrote:
By processes the messages one by one, do you mean My message B has to be
wait until message A gets
26 matches
Mail list logo
