How do people on the list use a debugger on Akka applications? I find when
a breakpoint is hit and threads are stopped, any remote or cluster
connections time out and errors occur. Is there any way, short of disabling
or lengthening timeouts, to get this to work?
I'm using IntelliJ with the Sc
Yes, that's the only way I've found to do it for now.
On Saturday, November 15, 2014 11:06:05 AM UTC-7, Martynas Mickevičius
wrote:
>
> Hi Curtis,
>
> when debugging concurrent systems I find that extensive debug logging is
> really helpful. :)
>
> On Fri,
Hi, been having great luck with Akka so far but I can't figure this one out.
I have a JVM app with two actor systems, let's call them AS and BS. AS is
created first. I also have a remote actor system called RS in another JVM.
AS sending messages to RS is no problem and RS can reply using the sen
tcp {
hostname = ""
port = 0
}
}
}
}
On Friday, April 11, 2014 4:45:08 PM UTC-6, √ wrote:
>
> All your ActorSystems need to use Remoting. I don't see anywhere in your
> post where you explain what RS has in terms of config.
&
I was trying to simplify it but there is another server MS at a known port
that RS registers at. I guess my main question is, should this work? I
assume at some point the BS actors ActorRef gets converted from local to
remote. Somewhere on the trip, it gets converted to an actor in AS even
thou
> actorSelection or otherwise (for bootstrap)
>
>
> On Sat, Apr 12, 2014 at 1:20 AM, Curtis Stanford <
> cur...@stanfordcomputing.com > wrote:
>
>> I was trying to simplify it but there is another server MS at a known
>> port that RS registers at. I guess my main
Ahhh, I didn't think of that. Not sure that's the problem but it gives me
something to look into.
Thanks very much!
On Friday, April 11, 2014 5:47:22 PM UTC-6, √ wrote:
>
>
>
>
> On Sat, Apr 12, 2014 at 1:43 AM, Curtis Stanford <
> cur...@stanfordcomputing.com &g
If I got a remote ActorRef from RS in one actor system, could I use it in
another actor system?
On Friday, April 11, 2014 5:49:47 PM UTC-6, Curtis Stanford wrote:
>
> Ahhh, I didn't think of that. Not sure that's the problem but it gives me
> something to look into.
&
Yah, that was the problem. Apparently, I can't share even remote actor refs
between systems. Solved it by sharing the actor path instead and using
context.actorSelection(path)
Thanks for all your help.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>
when sending to a remote ActorRef then the
> system which created that ref would run the serialization of the message
> (including the sender ref). If you are observing this behavior with a
> newer version of Akka then something else is wrong.
>
> Regards,
>
> Roland
&g
I've been reading up on akka persistence and have a few questions, if I may:
1. What is the problem persistence is meant to solve? Is it just to be able
to recover actors after an error or crash or are there uses beyond that?
The Scala Days 2014 talk hinted at some kind of link between persisten
Wow, thanks for the great info! I like the write model/read model way of
thinking. Very helpful. I'm guessing that using the default LevelDB
persistence store is not sufficient for large-scale applications?
On Tuesday, July 8, 2014 5:24:12 PM UTC-6, Konrad Malawski wrote:
>
> Hello Curtis!
> Rep
I'm wondering about granularity. Let's say you are keeping track of Users.
Do you have a persistent actor for the collection of users or one
persistent actor for each user? The latter could end up with a lot of
actors, no?
Curtis
--
>> Read the docs: http://akka.io/docs/
I see. What I'm thinking of is more of an administration function where
administrators can add/change/delete users and I want the user information
in memory and be able to sync with a client. So, the client would have the
list of users in a GUI and be able to pick and change users as needed.
Th
14 matches
Mail list logo
