9 maj 2014 kl. 07:53 skrev Andreas Gies andreas@googlemail.com:
Hi Roland,
before I answer I should say that I haven't tested the approach you have
suggested as of yet and therefore its more like a theoretical exercise for
now. I'll try to explain the concern I have:
Most of my
Thanks!
Good do know!
Frankly speaking I was a little bit confused by the results :)
Regards
Wolfgang
Am Donnerstag, 8. Mai 2014 14:39:41 UTC+2 schrieb Akka Team:
Hi Wolfgang,
that is obviously a bug https://github.com/akka/akka/issues/15149,
thanks for noticing! For reference, it is
On 09.05.14 09:25, Roland Kuhn wrote:
9 maj 2014 kl. 09:08 skrev Martin Krasser krass...@googlemail.com
mailto:krass...@googlemail.com:
On 09.05.14 08:41, Roland Kuhn wrote:
Hi Martin,
9 maj 2014 kl. 08:05 skrev Martin Krasser krass...@googlemail.com
mailto:krass...@googlemail.com:
9 maj 2014 kl. 09:58 skrev Martin Krasser krass...@googlemail.com:
On 09.05.14 09:25, Roland Kuhn wrote:
9 maj 2014 kl. 09:08 skrev Martin Krasser krass...@googlemail.com:
On 09.05.14 08:41, Roland Kuhn wrote:
Hi Martin,
9 maj 2014 kl. 08:05 skrev Martin Krasser
@Giovanni it could be the idle status in my case, too. My app is rarely used
and I have an actor per shard, which makes them even less used.
@Roland This is an interesting point. My setup is very basic. No cluster, no
extra config, not even high-load and still there's a chance of loosing reply
9 maj 2014 kl. 10:31 skrev Muki nepomuk.sei...@gmail.com:
@Giovanni it could be the idle status in my case, too. My app is rarely used
and I have an actor per shard, which makes them even less used.
@Roland This is an interesting point. My setup is very basic. No cluster, no
extra
If I understand it you question it is about:
scala RemoteSystem.remoteActor ! Start(RemoteSystem.clusterActor)
and why the singleton actor receives sender path with wrong system name.
You are doing something that is not supported. You grab an ActorRef
belonging to one ActorSystem and use that
Hi Roland,
We use Channel in conjunction with Eventsourced Processor (EP) in our
applications in receiveRecover.
It would be sad to see it go away without a reasonable alternative.
One scenario in our apps is that we use DDD/ES and have a lot of EPs of
same type, e.g. 1 instances,
that
Hi,
I am currently trying to figure out how to best test whether an actor
throws an exception. The only solution I can think of is creating that
actor as a child of another actor and use the standard supervision to
somehow propagate the exception to the test code (probably there are
several
Nothing like that in TestKit, reason being - you don't usually interact
with Actors like that. I think the test should feel more like when this
happens, will it be restarted by it's parent? etc.
I'd rather structure the test like that, but maybe there's something I'm
missing in your use-case.
On
Hi all,
Interesting discussion. I have no problem removing command sourced
Processor from user API, with the added capabilities of
EventsourcedProcessor. I have thought of P as a low level building block
and only to be used for simple write-ahead-log scenarios. External
side-effects during replay
I don't think it's a matter of my use-case, I think it's a matter of test
case granularity. In my system, I throw the Exception because I want the
parent to act upon it, so it's part of the actors API. However, I tend to
test actors in isolation, i.e., I want to test the child alone and make
How about extracting the actor’s behaviour to a trait, and test that trait for
the expected throw behaviour using plain old ScalaTest `intercept[Exception] {
… }`, would it make sense in your case or are the interactions “very relying on
the thing being an actor”?
Having that said, it’s just
Hello,
I am sure I am missing something obvious, but I don't see it. I created a
simple priority mailbox similar to the one in the doc:
package services;
...
public class PriorityMailbox extends UnboundedPriorityMailbox {
public PriorityMailbox(ActorSystem.Settings settings, Config config)
On Thu, May 8, 2014 at 5:35 PM, Lawrence Wagerfield
lawre...@dmz.wagerfield.com wrote:
Fascinating and very helpful!
Out of interest, where does RAFT sit on the aforementioned spectrum? I
only ask as there's a few Akka RAFT implementations floating around...
We have not talked about
On Thu, May 8, 2014 at 10:28 PM, Akka Team akka.offic...@gmail.com wrote:
Hi Ashley,
it is good that you ask these questions! [answers inline]
On Tue, May 6, 2014 at 8:28 AM, Ashley Aitken amait...@gmail.com wrote:
I thought reactive applications were all event-based and, in particular,
Hi,
Am Freitag, 9. Mai 2014 13:34:50 UTC+2 schrieb Konrad Malawski:
How about extracting the actor’s behaviour to a trait, and test that trait
for the expected throw behaviour using plain old ScalaTest
`intercept[Exception] { … }`, would it make sense in your case or are the
interactions
Hi Carsten,
9 maj 2014 kl. 14:50 skrev Carsten Saathoff cars...@kreuzverweis.com:
Hi,
Am Freitag, 9. Mai 2014 13:34:50 UTC+2 schrieb Konrad Malawski:
How about extracting the actor’s behaviour to a trait, and test that trait
for the expected throw behaviour using plain old ScalaTest
9 maj 2014 kl. 14:57 skrev Chanan Braunstein chanan.braunst...@pearson.com:
Since you asked for feedback:
We are using EventsourcedProcessor and have no plans to use Processor. We saw
the benchmarks and read the docs that Processor is faster, but choose to
model our system using
Hello!
I'm wondering if there's an example of cluster ciient usage available in
sources? I've read the doc at
http://doc.akka.io/docs/akka/2.2.3/contrib/cluster-client.html and it's not
clear how to use that in case if the cient is started in a separate JVM
outside of a cluster.
For example,
Hi,
I followed the Advanced akka course in the last 2 days (which was awesome
by the way) and noticed something of the API which I think can be improved.
When you start the ClusterSharding its return type is Unit and you have to
retrieve the ShardRegion by calling the shardRegion on
On Sunday, April 20, 2014 4:59:22 PM UTC+2, Patrik Nordwall wrote:
The User actor persist FirstNameChanged, and inside the persist block it
sends a Persistent(FirstNameChanged) message to the AllUsers Processor. On
the query side we have a AllUsersView connected to that processor. When
On Fri, May 9, 2014 at 4:43 PM, Jeroen Gordijn jeroen.gord...@gmail.comwrote:
Thanks Patrik, I overlooked that it is blocking, that makes the fix even
easier. You mention that you would not do it in the same place and I don't
have enough experience to comment on that, but in the course it
Hi Liang,
the ActorSystem creates the Actor, not the other way around. You might want to
check some basic Activator tutorials to see some examples:
https://typesafe.com/activator/template/hello-akka
or check the lower left of http://akka.io/downloads/
Regards,
Roland
9 maj 2014 kl. 16:48
On Friday, May 9, 2014 4:37:16 PM UTC+2, Olger Warnier wrote:
On Friday, May 9, 2014 4:29:32 PM UTC+2, Paweł Kaczor wrote:
On Sunday, April 20, 2014 4:59:22 PM UTC+2, Patrik Nordwall wrote:
The User actor persist FirstNameChanged, and inside the persist block it
sends a
On Friday, May 9, 2014 5:58:42 PM UTC+2, Paweł Kaczor wrote:
On Friday, May 9, 2014 4:37:16 PM UTC+2, Olger Warnier wrote:
On Friday, May 9, 2014 4:29:32 PM UTC+2, Paweł Kaczor wrote:
On Sunday, April 20, 2014 4:59:22 PM UTC+2, Patrik Nordwall wrote:
The User actor persist
On Fri, May 09, 2014 at 04:03:26PM +0200, Patrik Nordwall wrote:
In the log you posted I see that the problem is that localhost is not the
same thing as 127.0.0.1. You must use the hostname you specfied in config
akka.remote.netty.tcp.hostname
Thanks, Patrik!
--
Eugene N Dzhurinsky
9 maj 2014 kl. 18:46 skrev Eugene Dzhurinsky jdeve...@gmail.com:
On Fri, May 09, 2014 at 04:03:26PM +0200, Patrik Nordwall wrote:
In the log you posted I see that the problem is that localhost is not the
same thing as 127.0.0.1. You must use the hostname you specfied in config
Maybe we could have `start` return an `ActorRef` immediately, i.e. an
asynchronous operation like `actorOf`?
Heiko
On Fri, May 9, 2014 at 4:48 PM, Patrik Nordwall
patrik.nordw...@gmail.comwrote:
On Fri, May 9, 2014 at 4:43 PM, Jeroen Gordijn
jeroen.gord...@gmail.comwrote:
Thanks
9 maj 2014 kl. 18:54 skrev bhudgeons bran...@atsoft.at:
Patrik,
Thanks for the explanation. So, when you say:
On Thu, May 1, 2014 at 9:04 PM, bhudgeons bra...@atsoft.at wrote:
Santoash,
It is certainly possible, but it is confusing. I think what is probably
happening is
Lawrence - were you wondering where the existing Akka-based Raft
implementations (eg. ktoso/akka-raft https://github.com/ktoso/akka-raft)
sit in Roland's auto downing to no downing spectrum and/or if RAFT has any
particular consistency requirements that map to one of Roland's categories?
I'm
I think you misunderstood what cluster events are for.
MemberUp/Down aren't fired when your actors come up, they're fired when a
new member joins the cluster. If you want an actor to know when another
actor is ready, you need to explicitly send a message. You can however use
DeathWatch to
On Fri, May 09, 2014 at 05:18:09PM -0700, Ryan Tanner wrote:
I think you misunderstood what cluster events are for.
MemberUp/Down aren't fired when your actors come up, they're fired when a
new member joins the cluster. If you want an actor to know when another
actor is ready, you need to
yes now I just using the context.child(name),cause I found that actorCell
is using TreeMap,so if I want to achieve O(1),should I put an hashMap In my
Actor implement?I found just as what you said,the RouterLogic is not the
right approach for me.
thanks for the answer
在
Hi ,I have done this with right an Play plugin and api implement the api in
the plugin,
the implement just forward the request to the inner actor of the plugin.
在 2014年5月8日星期四UTC+8下午5时59分01秒，faisal...@gmail.com写道：
Hello all,
I am working on a fairly complicated system, and using Akka to
35 matches
Mail list logo
