On 19.03.14 15:38, Manas Kar wrote:
Hi Martin,
I have a process that is running since last Sunday evening using the
above code base(Given here
http://stackoverflow.com/questions/22315418/akka-persistentchannel-does-not-delete-message-from-journal-upon-confirm)
. The journal space has grown
On Thu, Mar 20, 2014 at 12:56 PM, Allan Brighton allane...@gmail.comwrote:
Hi Patrik,
It turns out that this line was the problem:
unmanagedSourceDirectories in Test += baseDirectory { _ / src /
multi-jvm / scala },
I added it to fix a problem in the generated Idea-13.1 projects,
Hi,
I have a question about the Circuit Breaker's behaviour, specifically how
the callTimeout parameter interacts with failures being counted
It seems that the Circuit Breaker doesn't register a failure until the call
is completed, rather than when the call takes longer than the callTimeout
Hi Will,
On Fri, Mar 21, 2014 at 4:19 AM, wpalah...@gmail.com wrote:
Hi,
I have a question about the Circuit Breaker's behaviour, specifically how
the callTimeout parameter interacts with failures being counted
It seems that the Circuit Breaker doesn't register a failure until the
call
Hi,
Sorry for the delay.
Which version of Akka are you using? If possible, use latest stable
release, i.e. 2.3.0.
Failure detection can be triggered by that the worker nodes are
unresponsive. As you see in the logs heartbeat messages are sent to monitor
the remote system. If it doesn't reply in
Hi Kal,
On Thu, Mar 20, 2014 at 10:00 PM, Kallin Nagelberg
kallin.nagelb...@gmail.com wrote:
Would it be safe to say that Akka is no longer an appropriate framework
for such a simulation?
I'm not familiar with the ant simulation. If it requires transactions
across actors it is probably
My rule of thumb is: if you don't know why tell wouldn't work, don't use
ask. :)
On Mar 21, 2014 12:50 PM, glidester glides...@gmail.com wrote:
Hi,
I'm in the process of learning Akka and I wondered if anyone could clarify
something for me.
If I have 2 actors. I 'ask' Actor A which in turn
Hello there,
In general always perfer tell (!) instead of ask (?), unless you have a
compelling reason not to. It has less overhead, and I also find things nicer to
model using plain actor tell's instead of ask's - which mix up styles a little
bit (actors in general fire and forget).
But
Finally got around to push it to
github: https://github.com/michaelpisula/akka-journal-inmemory
Runs successfully against the persistence-testkit.
Cheers,
Michael
Am Montag, 17. März 2014 09:46:53 UTC+1 schrieb Akka Team:
Hi Michael,
sounds like a very interesting tool to have. Even if it
Hi again,
I have tried the CreationApplication from the remote sample on two server
machines. I can't reproduce what you have reported, but I can see that the
CalculatorActor doesn't detect that the parent CreationActor has crashed.
That is a known problem and the fix is on the
Ok, so it seems people prefer tell to ask. The only reason I'm using ask is
that the example I'm working from
http://doc.akka.io/docs/akka/snapshot/scala/testing.html#Testing_the_Actor's_Behavior
uses
ask.
I'm writing some unit tests to test my Actor 'a' calling Actor 'b'. My
Actor 'b' is
How fast does the blockingExecute take?
On Fri, Mar 21, 2014 at 4:35 PM, glidester glides...@gmail.com wrote:
Ok, so it seems people prefer tell to ask. The only reason I'm using ask
is that the example I'm working from
Hi,
I have an actor that sends some messages to self
for(instance-0 until numberOfInstances) self ! Event1(instance,0,date)
This is how I'm creating the actor in question:
context.actorOf(Props(new OffHeap(date,populationSize,isLast)),oh.concat(
date))
I'm getting DeadLetters,
Does it terminate before processing all of its messages?
On Fri, Mar 21, 2014 at 5:16 PM, Bruce bmfergu...@mac.com wrote:
Hi,
I have an actor that sends some messages to self
for(instance-0 until numberOfInstances) self ! Event1(instance,0,date)
This is how I'm creating the actor in
Yes that was it! Thank you so much Konrad.
On Friday, March 21, 2014 4:14:28 PM UTC, Konrad Malawski wrote:
The reason might be that you're calling sender() inside the Future's map.
The sender() call is only valid *within* the actor itself, and this
construction (f map { sender ! ... })
I only showed 7 of 30 messages, all of which generate a DeadLetter. The
app does not appear to terminate. At this point there really aren't any
other messages to process, so it's hard to tell. It doesn't crash, and it
does not appear to hang.
On Friday, 21 March 2014 12:19:57 UTC-4, √
How is that possible, that code was commented out?
On Fri, Mar 21, 2014 at 5:22 PM, glidester glides...@gmail.com wrote:
Yes that was it! Thank you so much Konrad.
On Friday, March 21, 2014 4:14:28 PM UTC, Konrad Malawski wrote:
The reason might be that you're calling sender() inside the
On Fri, Mar 21, 2014 at 5:25 PM, Bruce bmfergu...@mac.com wrote:
I only showed 7 of 30 messages, all of which generate a DeadLetter. The
app does not appear to terminate.
Not the app—the actor.
At this point there really aren't any other messages to process, so it's
hard to tell. It
I assumed the commented code was in the spirit of oh, and the commented stuff
didn't work out for me, plz help. :-)
--
Konrad Malawski
geecon.org / java.pl / krakowscala.pl / gdgkrakow.pl
From: √iktor Ҡlang viktor.kl...@gmail.com
Reply: akka-user@googlegroups.com akka-user@googlegroups.com
On Fri, Mar 21, 2014 at 5:34 PM, Konrad Malawski ktos...@gmail.com wrote:
I assumed the commented code was in the spirit of oh, and the commented
stuff didn't work out for me, plz help. :-)
But the quoted code should work?
--
Konrad Malawski
geecon.org / java.pl / krakowscala.pl /
D'oh! Of COURSE that's what you meant. ;-)
Logging of the life cycle doesn't show anything but the creation
2014-03-21 12:34:01,619 DEBUG [system-akka.actor.default-dispatcher-5]
c.e.o.OffHeap [Slf4jLogger.scala:77] started
(com.epoch6.offHeap.OffHeap@5bf9e31e)
I will see if I can
Neither the commented or uncommented versions worked for me (both gave time
out exceptions of one kind or another).
Konrad correctly pointed out that my commented out code did not work
because I was using the 'sender' reference outside of the actor (inside the
Future's map).
Changing the
On Fri, Mar 21, 2014 at 5:51 PM, glidester glides...@gmail.com wrote:
Neither the commented or uncommented versions worked for me (both gave
time out exceptions of one kind or another).
Ok, what did blockingExecute do then?
Konrad correctly pointed out that my commented out code did not
On Thursday, March 20, 2014 2:49:28 PM UTC-4, √ wrote:
Yeah, using Death Watch is appropriate. One solution: if you use Akka
Cluster then it is easy to find the next master deterministially by just
scanning the membership list in order and using the first node that has an
appropriate
Hi all,
We are getting intermittently a [actor name [joinSeedNodeProcess] is not
unique!] exception at the akka Cluster system start up.
The production setup is a akka Singleton cluster deployed on 12 tomcats across
3 physical machines (4 nodes on every machine).
Do you have any idea how
Always upgrade to at least the latest bugfix release for the version of
Akka you are using and see if that resolves your problem.
Did that solve it?
On Fri, Mar 21, 2014 at 6:37 PM, Ryadh khsib riadh.kh...@gmail.com wrote:
Hi all,
We are getting intermittently a [actor name
Hi All-
This issue is a repost from a stack overflow
questionhttp://stackoverflow.com/questions/22547889/akka-actors-and-clustering-im-having-trouble-with-clustersingletonmanager-unhaI
currently have, but Patrik
Nordwall http://stackoverflow.com/users/1835220/patrik-nordwall suggested
I post
Solved. I was matching on the wrong tuple element, and hadn't provided a
default match case.
On Friday, 21 March 2014 12:40:29 UTC-4, Bruce wrote:
D'oh! Of COURSE that's what you meant. ;-)
Logging of the life cycle doesn't show anything but the creation
2014-03-21 12:34:01,619 DEBUG
Thanks for the quick reply Patrik,
I've created the ticket here:
https://www.assembla.com/spaces/akka/tickets/3950#/activity/ticket:
-Will
On Friday, March 21, 2014 4:16:31 AM UTC-5, Patrik Nordwall wrote:
Hi Will,
On Fri, Mar 21, 2014 at 4:19 AM, wpal...@gmail.com javascript: wrote:
Hello I am getting stuck on building Actors with Maven
I would like to bundle everything into a single JAR. But when I do this,
Akka code can no longer find the reference.conf files from the libraries.
I am using the net.alchim31.maven scala-maven-plugin and marking all
dependencies as
Hi Peter,
May I interest you in reading the documentation?
http://doc.akka.io/docs/akka/2.3.0/general/configuration.html#When_using_JarJar__OneJar__Assembly_or_any_jar-bundler
Cheers,
V
On Mar 21, 2014 10:10 PM, Peter Wolf opus...@gmail.com wrote:
Hello I am getting stuck on building Actors
But reading it again... It seems to recommend that I manually create a
reference.conf that is a merge of those from all the libraries.
Is that really all that shade does?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
Thank you Victor,
Yes I had read that documentation, and I do have the shade plugin in my
pom.xml
Unfortunately, it does not seem to work :-(
Here is my settings for it...
plugin
groupIdorg.apache.maven.plugins/groupId
Hi Peter,
I do not use Maven, and I unfortunately cannot foresee what does not work
actually yields.
Have you searched the mailing list archives for answers?
On Fri, Mar 21, 2014 at 10:25 PM, Peter Wolf opus...@gmail.com wrote:
Thank you Victor,
Yes I had read that documentation, and I do
I've never done any sort of TCP protocol implementation, and am looking at
Akka IO for this purpose.
I noticed here:
http://hseeberger.github.io/blog/2013/06/17/introduction-to-akka-i-slash-o/
that the handler actor calls context.watch()
// We need to know when the connection dies without
35 matches
Mail list logo
