That’s perfectly possible.
Yet you have to be careful to not close over any mutable actor state, e.g.
vars, ActorContext, sender(), etc. A good way to avoid that is define the flow
graph via a method in the companion object of your actor.
Heiko
--
Heiko Seeberger
Home: heikoseeberger.de
I have a flow graph that needs initialization and post processing. I'd like
to do this within an actor. The actor receives a message, the flow graph is
initialized, then the message is passed to it, then its result is sent to
different actors. I don't see this use case in the docs so I don't kno
I put this line in my application.conf testing project
akka.remote.netty.tcp.port = 0
Each actor system will bind a diffrent port and will run in parallel.
Em sexta-feira, 13 de novembro de 2015 10:58:49 UTC-3, Ian Phillips
escreveu:
>
> I'm after some advice as to best practice when setting up m
Thanks Patrick. You just saved me a few hours of research :)
I wonder if this kind of information would also be available through
ConductR?
tnks,
Rod
On Friday, November 13, 2015 at 1:19:21 PM UTC, Patrik Nordwall wrote:
>
> https://github.com/akka/akka/pull/18543
>
> it will be in upcoming 2.4
I'm after some advice as to best practice when setting up multiple
(ScalaTest) tests in an Akka project, I'm using a base class like so:
class BaseSpec extends TestKit(ActorSystem("application"))
with FlatSpecLike with Matchers with ScalaFutures with ImplicitSender with
BeforeAndAfterAll {
On Sun, Nov 8, 2015 at 6:36 PM, Adam Dohnal wrote:
> Hello,
>
> recently I read through new akka-persistence-query-experimental module and
> would like to see some tutorials and examples to see how it can work.
> Documentation is really abstract for me. Unfortunately, I'm not able to
> find any a
https://github.com/akka/akka/pull/18543
it will be in upcoming 2.4.1
/Patrik
On Thu, Nov 12, 2015 at 6:15 PM, Rodrigo Boavida
wrote:
> Brice,
>
> Thanks for the answer. I will definitely have a look into what the events
> could give me and how the strategy could be tuned to provide such events
On Tue, Nov 3, 2015 at 2:14 AM, wrote:
> It seems like the ShardCoordinator is started the first time a request is
> made to an Entity Actor belonging to the ShardCoordinator. This adds some
> latency to the first request made to an Entity Actor managed by the Shard
> Coordinator. I'm seeing > 3
That should not be the case. See
http://doc.akka.io/docs/akka/2.4.0/scala/routing.html#Senders
You don’t happen to use sender() from inside a Future callback or something
like that?
/Patrik
On Wed, Nov 11, 2015 at 10:01 PM, Eugene Dzhurinsky
wrote:
> Hello!
>
> I would like to clarify the poi
It looks like you have found the problem. The persistenceId must be unique,
and should include the entity identifier, which you can get from the name
of the supervisor actor (which is the entity from the sharding
perspective). You could use same name when creating the child, and then the
child woul
Hi Ricardo,
doesn't look like HttpsContext param is currently surfaced in the java
DSL's bindRoute.
This should be discussed in a ticket.
Cheers
André
On Thursday, November 12, 2015 at 6:57:38 PM UTC+1, Ricardo Silva wrote:
>
> Hello,
>
> is it possible to have a server handling https connecti
Given that tehre a lot of methods that use locks in the implementation, do
syscalls etc, it eveyrthing looks like sync calls then all callsites could
be a potentially blocking operation. :S
On Wed, Nov 11, 2015 at 5:15 PM, 'Konstantinos Kougios' via Akka User List <
akka-user@googlegroups.com> wro
12 matches
Mail list logo