On 07.05.14 17:10, Matthew Howard wrote:
On Wednesday, May 7, 2014 12:57:23 AM UTC-4, Martin Krasser wrote:
Please not that the primary use case for persistent channels is to
deal with slow and/or temporarily available
consumers/destinations. It is not optimized for high
On 08.05.14 08:23, Raymond Tay wrote:
Hi all,
Was wondering whether LevelDB supports multiple yet distinct
processors into the same journal within the same `ActorSystem` ?
Sure, they only must have different processorIds. An application only
has to make sure that it doesn't have several
Hello Hakkers,
I am working on an application that uses OSGI under the covers for its
modularization requirements. I have a scenario where a bundle provides an
actor that gathers events and redistributes them to a group of listeners.
In OSGi the gathering actor may come and go. While it is
Hi Erich,
the PersistenceSpec trait is targeted at the akka-persistence test suite (since
it uses AkkaSpec which is not part of the published artifacts), so your
uncertainty is understandable. EventsourcedProcessors are in principle tested
just like normal actors, with the complication that
Hi Arvind,
what have you tried and which error messages did you get? Which versions of
Play, Akka, Java, Ubuntu are you using and how are you starting your Play
application?
Please note that the Console is discontinued in favor of embedding the
development monitoring into Activator (take a
Hi Eduardo,
there are several parts which will have to play together in relation to
your requirement of avoiding delay during a failover:
- first you need to decide that you want to fail over, which means that
the backup needs to determine that it has to become active
- then you need to
Hi
I've found a new thing to worry about :-)
If I use an eventsource model and content myself with the default
serialization and akka persistence, what's the likelihood of my serialized
objects becoming unreadable in the future? What's the long-term stability
of the default akka serialization
Thanks Martin. Found out after merging the sample code from akka-cluster
and akka-persistence. The gist is
here: https://gist.github.com/raygit/926cc3764abdec86de12 if anyone cares
to read it, simple and illustrative.
On Thursday, May 8, 2014 2:28:07 PM UTC+8, Martin Krasser wrote:
On
On 08.05.14 11:21, Raymond Tay wrote:
Thanks Martin. Found out after merging the sample code from
akka-cluster and akka-persistence. The gist is
here: https://gist.github.com/raygit/926cc3764abdec86de12 if anyone
cares to read it, simple and illustrative.
Thanks for sharing!
On Thursday,
On Thu, May 8, 2014 at 9:02 AM, benoit heinrich
benoit.heinr...@gmail.comwrote:
Hi Patrik,
Thanks for the answer and please find my notes below:
That is very interesting. We had a similar problem that was fixed in Akka
2.3.2. I can see that you use 2.3.2, but would it be possible that you
I read this tweet from Martin Krasser this morning:
#Akka-persistence is optimized for making stateful actors durable (at very
high transaction rates), not for implementing durable queues
I am confused as akka-persistence is comparable to other event sourcing
Hi Erich,
On Thu, May 8, 2014 at 8:22 AM, Roland Kuhn goo...@rkuhn.info wrote:
Hi Erich,
the PersistenceSpec trait is targeted at the akka-persistence test suite
(since it uses AkkaSpec which is not part of the published artifacts), so
your uncertainty is understandable.
Hello all,
I am working on a fairly complicated system, and using Akka to orchestrate
the process flow. One of the steps requires human intervention, and I was
thinking that I would use play framework to manage it. However, I am unable
to wrap my head around how will the general Akka system
Hi Brice,
the Routers (as in those which bypass the head actor’s mailbox) are meant
for a very specific use case, and their optimizations come with certain
restrictions as you discover. What you want to achieve can be done by using
the RoutingLogic inside a regular router, which gives you all the
Since Akka 2.3.0 there is a separation between routing logic and the
previous “Router” package: what the example constructs with “new Router” is
not an actor, it is just a data structure which knows the routees and
dispatches messages to them according to the provided RoutingLogic
instance. This
Hi Wolfgang,
that is obviously a bug https://github.com/akka/akka/issues/15149, thanks
for noticing! For reference, it is fully reproducible in the REPL
scala
system.actorSelection(akka.tcp://server127.0.0.1:2567/user/DummyActor) ?
Identify(42) onComplete { case x = println(x) }
scala
Hi Ulf,
from what you show it is impossible to gain more insight or give good
advice. The only thing I can tell you is that the log line is not printed
or generated by Akka (we don’t have SEVERE). If asking for help on an open
forum like this one is not something that you can practically do, you
Hi Andreas,
the mechanism we foresee for this case is that you create an appropriate
ClassLoader which has visibility into all the right bundles (e.g. using the
BundleDelegatingClassLoader from the akka-osgi package) and pass that to
the ActorSystem at creation. We have taken care that all
No, this happens with several actors, not related to db connections.
One thing we have observed is that happens after the Play application has
been idle for a long period.
Thanks
Giovanni
On Thursday, May 8, 2014 12:25:47 AM UTC+2, Muki wrote:
Hi,
I have similar problems with play. The
Hi Nicola,
thanks for providing the sample project, I tried it out and the problem is
that the FSM never processes a single message when instantiated in a
TestFSMRef. It works fine if you change it to system.actorOf(Props(new
...)) and then rely on SubscribeTransitionCallBack to monitor the
thanks Roland for taking care of it.
What about the second part of my email concerning the problem I have
recovering the PersistentFSM:
--
There are also three objects that you can run
FiniteStateMachineSpes - Main
AlmostPersistentFSMSpec
Wow, that is quite a project, thanks for sharing! Reading the
AkkaIntegration page I nodded on several occasions, the way you integrate
the two worlds sounds plausible (with the caveat that I have not actually
tried it out), but especially the separation in Actor- and Service-bundles
resonates
Hi Roland,
thanks for your response. IMHO that sounds a bit un-OSGi. For example I am
working on a family of applications, some of which have spray
functionality, some which don't. If I understand you correctly, I would
have to choose a different Classloader config for each container variant
Hi Roland,
I am happy you like it. Its ongoing work, but I have created a pull request
for the community page.
Best regards
Andreas
Am Donnerstag, 8. Mai 2014 15:35:30 UTC+2 schrieb Akka Team:
Wow, that is quite a project, thanks for sharing! Reading the
AkkaIntegration page I nodded on
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...
On Monday, May 5, 2014 7:07:16 AM UTC+1, shikhar wrote:
I have been hacking on a discovery plugin for
Guys,
First Question:
I have a question related to Multiple client remoting. Assume we have a
server actor is started with its hostname and port. I need to launch
multiple client actors to report worker status to this server. These
clients actors don't receive any remote messages, and only
Faisal,
that does of course depend on your architecture. But it should be quite
simple. You can either use Play for your main application that starts your
own Akka System in the Global object. Or you use Play's Akka. What I
personally use is also Akka remoting where you use remote Akka
The way you would approach this depends very much on what you want to
achieve: is it enough if your router can handle a million messages per
second? If that is the case then I would recommend just writing your own
actor implementing exactly what you want, not using any of the RouterLogic
Say for a typical web application you add a message on a queue so the
operation is performed in a asynch nature for things like:
- sending registration email
Normally I write a message to a queue, and then a background worker would
pull the message from the queue and then send the email.
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,
events could be generated and flow through an application from GUI back to
Hi Miguel,
the actor you show does not buy you much, since the supervision aspects do
not come into play (i.e. failures will happen in a future, not in the
actor). I would recommend just calling the webservice from the other actor
which needs the reply.
Regards,
Roland
On Wed, May 7, 2014 at
Hi Eugene,
could you clarify the use-case a bit more? Why would there be multiple
FSMs, where would the messages to be processed come from, why can’t you use
the work pulling
patternhttp://letitcrash.com/post/29044669086/balancing-workload-across-nodes-with-akka-2
?
One thing to note: saying
Thanks for the thoughtful reply Ronald!
On Tue, May 6, 2014 at 11:58 PM, Akka Team akka.offic...@gmail.com wrote:
Hi Shikhar,
thanks for sharing!
There are many possible ways of dealing with partitions in a distributed
system, and it depends very much on the use-case what the best
Hi Barry,
this means that `context` must have been null, which cannot really be. You
cannot by chance upgrade to a later version, preferably 2.3.2? There were
some things that were fixed in ActorCell within the past two release
cycles, but I do not recall this particular problem (which basically
On Thu, May 08, 2014 at 10:37:21PM +0200, Akka Team wrote:
Hi Eugene,
could you clarify the use-case a bit more? Why would there be multiple
FSMs, where would the messages to be processed come from, why can’t you use
the work pulling
Sometimes things take time, and somethings messages can also be lost (Akka
does at-most-once delivery), so an ask() timing out is something that you
will need to expect and handle, even if it should happen rarely.
Regards,
Roland
On Thu, May 8, 2014 at 3:08 PM, Giovanni Ruggiero
On Thu, May 8, 2014 at 3:26 PM, Nicola Piccinini piccin...@gmail.comwrote:
thanks Roland for taking care of it.
What about the second part of my email concerning the problem I have
recovering the PersistentFSM:
I think it might well be coupled with the other issue, it seems that the
Hi Andreas,
OSGi is an area where I am frequently learning new things, so you might
want to amend my world view: when you start an application, there will be
some bundle which depends on a bunch of other bundles to perform all its
functions, there will be transitive dependencies etc. What I had
On Thu, May 8, 2014 at 4:04 PM, Andreas Gies andreas@googlemail.comwrote:
Hi Roland,
I am happy you like it. Its ongoing work, but I have created a pull
request for the community page.
Thanks, merged!
Regards,
Roland
Best regards
Andreas
Am Donnerstag, 8. Mai 2014 15:35:30
What about the second part of my email concerning the problem I have
recovering the PersistentFSM:
I think it might well be coupled with the other issue, it seems that the
TestFSMRef somehow mixes up the Processor internals.
but that should not be related in any way with the tests.
I am
Hello, all!
Is there any update on this topic, like - was this log level implemented in
Akka slf4j bridge?
As far as I can see, no - so what's the status?
Thanks!
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Very helpful, thanks Martin.
--
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
Ok, so I've been struggling with this same issue for a few days now. I've
used uni-directional Akka actors from Play 2.2.2 to start some background
tasks that just blindly run. This is the first time I had a need to do
something more complex and while the docs are very abundant I couldn't
Yes true, I do have allot of worker/job features that I could put into Akka
but I am very fresh and really have no idea about it yet.
If there is a web ui hook into Akka that I can view what jobs have been
completed or their state that would be ideal.
The issue is most of my work will require
Patrik,
Could you take a look at this gist (and the first comment)? I've
reproduced my experience with this issue. Perhaps I'm doing something
wrong.
Thanks!
https://gist.github.com/bhudgeons/78cc89fb6be47ff1c975
On Friday, May 2, 2014 10:07:52 AM UTC-5, bhudgeons wrote:
I had the same
Hi Leon,
8 maj 2014 kl. 09:09 skrev Leon Ma tutuf...@gmail.com:
Ah, the compile actually green, while IntelliJ complains about Can not
resolve method Props.apply.
Could you point me to the right apply method?
What do you mean? You are using the right method, it is just IntelliJ that has
a
Hi Liang,
8 maj 2014 kl. 18:08 skrev Liang Tang liang.x...@gmail.com:
Guys,
First Question:
I have a question related to Multiple client remoting. Assume we have a
server actor is started with its hostname and port.
You mean ActorSystem, right?
I need to launch multiple client actors
8 maj 2014 kl. 23:06 skrev Eugene Dzhurinsky jdeve...@gmail.com:
On Thu, May 08, 2014 at 10:37:21PM +0200, Akka Team wrote:
Hi Eugene,
could you clarify the use-case a bit more? Why would there be multiple
FSMs, where would the messages to be processed come from, why can’t you use
the
Hi Eugene,
see this ticket:
https://www.assembla.com/spaces/akka/tickets/3651?comment=422208093
In short, within Akka I don’t see a reason to introduce it, but you can easily
use implicit classes to enable `log.trace(...)` and create your own
Slf4jLoggingAdapter (by copying the Akka one and
Hi Tony,
that might work most of the time ;-) The problem is that the actor’s liveness
might easily change between your Identify and the tell or actorOf call. A
better approach is to create one supervisor for this type of job that always
exists; keep the reference to that one in a Play Plugin
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 applications today are in retail space or within the airport
industry (funny
51 matches
Mail list logo
