You can set context time out for actors, if they don't receive a message
within some time passivate them, activate them at login, that way you don't
have to lazy load when the player is active but at login which will
basically happen asynchronously.
Now, Akka experts should tell us if setting
For us, the issue was ultimately a symptom of the problem referenced here:
https://groups.google.com/forum/#!topic/akka-user/4lBUX7N7W6k
Our cluster was in a broken state and persistent actors were unable to
recover.
Patrik, if I read correctly this issue is resolved in 2.4? If so, would
still
Hi,
I didn't find a counterpart of mapRequestContext in akka-http, so I just
allow all the methods I have in my route. Here is my shot at CORS in
akka-http:
import akka.http.scaladsl.model.HttpMethods._
import akka.http.scaladsl.model.HttpResponse
import akka.http.scaladsl.model.headers._
I have heard from another co-worker that Akka remoting is very difficult on
Mesos using Docker, because of the random ports that it uses to connect.
Docker expects you to specify which ports are going to be used by your
container, and if you don't know ahead of time it can be difficult to
Yeah, I was thinking about using a FlexiMerge/FlexiRoute approach on top of
the bidi flow to switch from placebo to normal flow. I will update if/when
I have a working result.
On Monday, June 15, 2015 at 3:46:03 PM UTC-5, rkuhn wrote:
Given how hard it was to get TLS implemented in the first
I also made an example of this in a recent Akka HTTP showcase I toyed with.
Client-side Scala.JS to upload is here
https://github.com/cretz/scala-web-ideal/blob/1f45cb3d71f0f0690b6b551a8d1de16f45263c57/client/src/main/scala/webideal/upload/UploadJsImpl.scala#L134and
server-side Akka HTTP is
The specific case for persistence replay is fixed, but it would anyway be
nice if we used logger names that can filtered. Issue, yes please.
/Patrik
tors 18 jun 2015 kl. 17:44 skrev Grant Gavares gr...@makewonder.com:
For us, the issue was ultimately a symptom of the problem referenced here:
Hi,
We've been dealing with that kind of questions for the last months and
eventually ended up thinking that it's better to stick to Akka. It's true
that Camel gives you a plethora of connectors and integration patterns
right out of the box, but that benefits come with some costs. For
Akka team,
Are there plans to add support for HTTP/2 to Akka HTTP anytime soon?
Thanks
Heiko
--
Heiko Seeberger
Home: heikoseeberger.de http://heikoseeberger.de/
Twitter: @hseeberger https://twitter.com/hseeberger
Public key: keybase.io/hseeberger https://keybase.io/hseeberger
--
Read
Not short-term: first we must support HTTP/1.1, then we can think about the
next steps.
Regards,
Roland
18 jun 2015 kl. 21:18 skrev Heiko Seeberger loe...@posteo.de:
Akka team,
Are there plans to add support for HTTP/2 to Akka HTTP anytime soon?
Thanks
Heiko
--
Heiko Seeberger
It's been discussed a bit (most recently during ScalaDays),
with Play being the primary interested-party however we have not actively
looked into it yet.
It would definitely match our streaming http model very-very-nicely!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 18 June 2015 at
Akka 2.4 solves the docker problem with supporting an external address and
one internal.
--
Cheers,
√
On 18 Jun 2015 19:28, Jason Martens m...@jasonmartens.com wrote:
I have heard from another co-worker that Akka remoting is very difficult
on Mesos using Docker, because of the random ports
Hi all,
I'm seeing something very weird.
When I enable the logback turboFilter DuplicateMessageFilter:
http://logback.qos.ch/manual/filters.html#DuplicateMessageFilter
Hello,
I found a quite specific case involving Actors, Future callbacks and
exceptions where self becomes deadLetters.
I have the feeling I'm using self the way it is meant to be used, as
described
here: http://doc.akka.io/docs/akka/2.3.11/general/jmm.html#jmm-shared-state
Am I doing
Hello,
Are there any methods or tools that help detect cluster fragmentation?
Once fragmentation is detected what's the best practice to correct it?
Thanks,
Greg
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Actually that's not quite right...its not nearly that simple. These
oceans like Mesos need to auto-assign the ports so while, yes, 2.4 gives
dual binding capabilities this is only useful when you know the ports!
So how do you do that? That's much more complex.
I've got a hello-world remote
There's more... as context is also null in the Future's callback, anything
using context won't work, see below for an updated example using the Akka's
scheduler and dispatcher:
import akka.actor._
import scala.concurrent._
import scala.concurrent.duration._
case class Done(s: String)
case
Hi,
I'm working on a simple MMO game as a side project which is like Travian. I've
decided to use Akka as the game back-end, so I would like to share
my design with you. Your suggestions and feedbacks are very
appreciated.
Each of the following entities are
TCP is fundamentally a stream protocol, if you need to transmit messages that
are larger than one byte you will definitely have to implement a framing
protocol on top—that is not best practice but strictly required. The fact that
you get multiple bytes at once in your Actors is due to the O/S
Yes, I know that it's one of best practice when implementing tcp sockets
protocol. But I am using TCP Actors from Akka framework and there is no any
stream. I know that could fixing it by concatenation ByteString from
different TCP.Received message. But for me it looks like hack. Because it
Hi,
I'm also seeing this log message logged on a very unloaded cluster, on
akka 2.3.11.
On Wed, 2015-06-17 at 13:31 +0200, Patrik Nordwall wrote:
I'm interested in where all those resolve calls come from, because it
could be a performance issue. It could be deserialization of ActorRef.
It's
It is possible to start an actor in another remote ActorSystem, by using
the remote deployment feature. See this section of the documentation:
http://doc.akka.io/docs/akka/2.3.11/java/remoting.html#Creating_Actors_Remotely
You must still start the JVM and the ActorSystem separately.
An
22 matches
Mail list logo
