Re: [akka-user] Re: Akka Stream and Http 2.0-M1 Released!

Very glad the upgrade was so smooth for you Mathias! We know it's a bit of mechanical changes in some spots, but should be farily simple (and outlined in the migration guide). Happy hakking! --  Cheers, Konrad 'ktoso’ Malawski Akka @ Typesafe On 6 November 2015 at 22:34:26, Mathias Bogaert

[akka-user] Re: Keeping business logic and Actor system separate

When we first began using AKKA we had a similar approach and decided to put all the business logic in a service layer. This is a pretty standard Spring practice and it made testing a doddle - and also meant we could start writing the logic before we'd confirmed our favourite AKKA architecture.

[akka-user] Cluster Sharding - watching for termination of sharded actors.

Hi, We are using akka sharding extension for distributing message broker consumer actors over our cluster. Our in house consumer library, uses death watch on the consumers to manage it's state (when one of the actors connecting to the broker is moved to the other node, the supervisor no

Re: [akka-user] Re: persistentActor not receiving messages??

I've had a similar problem during creation of some multi node tests using leveldb as storage. The leveldb was misconfigured and my persistent actors crashed silently... Em sexta-feira, 6 de novembro de 2015 02:58:43 UTC-3, Patrik Nordwall escreveu: > > Didn't you see anything in the logs? I'm

Re: [akka-user] Re: deserializing ActorRef's after jvm restart, will it point to the correct actor?

This will be helpful. Is there any performance penalty compared to actorRef.tell ? If I cache ActorSelection (for say 10 secs) will it be better in terms of performance and also will avoid the server-restart issue? I see it has internally an anchor actorref, so it might be better On 06/11/15

[akka-user] Re: Akka shard entries is terminated

Caused by Kamon + Kryo not playing well if not all nodes has been weaved with Aspectj. On Monday, November 2, 2015 at 10:35:54 AM UTC+7, Hengky Sucanda wrote: > > Hi Guys, > > So i have been running Akka cluster sharding in production for a month now > (Akka 2.4, Play 2.4). My current set up

Re: [akka-user] Re: persistentActor not receiving messages??

completely silent. On Thu, Nov 5, 2015 at 11:58 PM, Patrik Nordwall wrote: > Didn't you see anything in the logs? I'm asking because if it is silent it > is something we must improve. > > /Patrik > > fre 6 nov. 2015 kl. 01:28 skrev Ian Holsman :

Re: [akka-user] Re: persistentActor not receiving messages??

Strange, I see this: [ERROR] [11/06/2015 16:49:48.776] [PersistenceSpec-akka.actor.default-dispatcher-3] [akka://PersistenceSpec/user/$a] null akka.actor.ActorInitializationException: exception during creation at akka.actor.ActorInitializationException$.apply(Actor.scala:172) at

Re: [akka-user] Re: deserializing ActorRef's after jvm restart, will it point to the correct actor?

Well, I refactored my code to cache actorpaths but indeed during creation all actorpaths are local and when they are transmitted over the wire they remain local => pointing to the wrong path. I've manually modified the address part of the path myself so that it contains the host & port of the

[akka-user] Re: Akka Stream and Http 2.0-M1 Released!

Excellent news!!! Thanks for the hard work, I'm gonna give it a try! El viernes, 6 de noviembre de 2015, 13:19:49 (UTC), Martynas Mickevičius escribió: > > *Dear Hakkers* > > we—the Akka committers—are very pleased to announce Akka Streams & HTTP > 2.0-M1, the first milestone of the upcoming

Re: [akka-user] Re: deserializing ActorRef's after jvm restart, will it point to the correct actor?

Ok so basically I am going to change my code and serialize endpoints (as strings) and then use a resolveOne(..) cache (probably cache refs for a short time of a few seconds) unless someone can recommend a better way. -- >> Read the docs: http://akka.io/docs/ >> Check

Re: [akka-user] Re: deserializing ActorRef's after jvm restart, will it point to the correct actor?

Thanks Martynas, I was afraid that this was the case. I would prefer to view actor paths as i.e. endpoints of a service, same path same service. I might serialize thousands of actorrefs and I suppose actorSelection for all those will take time as it requires network communication. So it is

Re: [akka-user] Re: deserializing ActorRef's after jvm restart, will it point to the correct actor?

You can send messages to ActorSelection without resolving them to ActorRefs. ActorSelection has ! and tell methods. On Fri, Nov 6, 2015 at 2:30 PM, Kostas kougios < kostas.koug...@googlemail.com> wrote: > Ok so basically I

Re: [akka-user] Re: deserializing ActorRef's after jvm restart, will it point to the correct actor?

hmm, I think actor paths will always be local during the time of the actor creation (all actors are created locally and then send over the wire). actor.path.address has a host & port of None, so there is no point sending that over the wire. The address part of the path won't automatically be

[akka-user] Re: Akka Stream and Http 2.0-M1 Released!

Great! On Friday, November 6, 2015 at 4:19:49 PM UTC+3, Martynas Mickevičius wrote: > > ... This is also the feature that will increase performance for various > use cases, including HTTP. > Is it just the first step, or significant part of the way, or almost the whole way to make Akka HTTP

[akka-user] Akka Stream and Http 2.0-M1 Released!

*Dear Hakkers* we—the Akka committers—are very pleased to announce Akka Streams & HTTP 2.0-M1, the first milestone of the upcoming 2.0 release. The overarching theme of this milestone is unification, both in internals and API. Thanks go to all of you who tried out Streams & HTTP 1.0, your

[akka-user] Re: Akka Stream and Http 2.0-M1 Released!

Great! Had to make only one change to my Akka HTTP API: replace akka.http.scaladsl.server.directives.UserCredentials with akka.http.scaladsl.server.directives.Credentials. On Friday, 6 November 2015 13:19:49 UTC, Martynas Mickevičius wrote: > > *Dear Hakkers* > > we—the Akka committers—are very