[akka-user] Akka 2.3.15 released!

Dear hAkkers, We—the Akka committers—are pleased to be able to announce the availability of Akka 2.3.15. This is the 15th maintenance release of the 2.3 branch. This release features fixes that have been gathered since the previous release, among which: Various fixed leaks: * Nepotism in Abstract

[akka-user] any plans to integrate ignite as a data grid with Akka ?

Hi All , is there any plan to have to integration between apache and akka or maybe using the cluster manager of Ignite to be the cluster manager of AKKA ? or cache access integration between Akka and Ignite data grid ? -- >> Read the docs: http://akka.io/docs/ >> Che

[akka-user] Akka on Android: akka.actor.ActorInitializationException

Hello Akka community! I'm trying to porting Apache Flink (which relays on Akka) to Android, but don't worry: you don't need to know this framework for this topic. While I was debugging, I caught a sendmessage() call in ActorCell.scala where the sender is null and mes

Re: [akka-user] Akka on Android: akka.actor.ActorInitializationException

Hi Luca, check the stack trace of the ActorInitializationException On Fri, Apr 1, 2016 at 10:02 AM, Luca Lovagnini wrote: > Hello Akka community! > > I'm trying to porting Apache Flink (which > relays on Akka) to Android, but don't worry: you don't need to know this >

Re: [akka-user] akka 2.4.2 [java] stopping http-server and flow handling IncomingConnection

When you say "cancel" do you mean "abrupt termination" or something with a code path attached to it? On Thu, Mar 31, 2016 at 11:53 PM, paweł kamiński wrote: > dont take it personally, there is a lot to process and sometimes it is > easy to overlook the most important part, I guess I didn't get t

Re: [akka-user] any plans to integrate ignite as a data grid with Akka ?

Hi Mahmoud, what would the benefits be? On Thu, Mar 31, 2016 at 4:32 PM, mahmoud romeh wrote: > Hi All , > > is there any plan to have to integration between apache and akka or maybe > using the cluster manager of Ignite to be the cluster manager of AKKA ? or > cache access integration between

Re: [akka-user] akka 2.4.2 [java] stopping http-server and flow handling IncomingConnection

I want to clean state of the app, so I could 1) terminate akka-system which would also terminate http-server and start it all over again. OR 2) I thought about shutting down just http-server in reaction to some fault state of actors hierarchy. Konrad's comment states that it is not enough ju

Re: [akka-user] akka 2.4.2 [java] stopping http-server and flow handling IncomingConnection

Call 'shutdown' on the ActorSystem? Or only the Materializer? On Fri, Apr 1, 2016 at 11:29 AM, paweł kamiński wrote: > I want to clean state of the app, so I could > > 1) terminate akka-system which would also terminate http-server and start > it all over again. > OR > 2) I thought about shuttin

Re: [akka-user] akka 2.4.2 [java] stopping http-server and flow handling IncomingConnection

Or wait until 2.4.3 and use the KillSwitch feature, as it was mentioned before: 1. unbind server 2. wait until grace period, then trigger KillSwitch.shutdown or abort 3. shut down ActorSystem -Endre On Fri, Apr 1, 2016 at 11:33 AM, Viktor Klang wrote: > Call 'shutdown' on the ActorSystem? Or o

[akka-user] Supervising Remote Actors

Hi, Is it possible to supervise remote actors? Since faults should be contained, asynchronously signaled and managed, will an exception thrown in the onReceive of a child actor be received in supervisor's strategy's apply() method? If yes, how are the exceptions propagated over the network?

Re: [akka-user] Supervising Remote Actors

http://doc.akka.io/docs/akka/2.4.2/scala/remoting.html#Creating_Actors_Remotely On Fri, Apr 1, 2016 at 12:05 PM, Jayesh Jadhav wrote: > Hi, > > Is it possible to supervise remote actors? Since faults should be > contained, asynchronously signaled and managed, will an exception thrown in > the on

[akka-user] Re: Can I use in-memory Actor state as a search engine ?

If you want to have an actor per domain object handled by akka-sharding for read/write and after each write update the indexes affected by that object for an in-memory map reduce engine which again one exist per akka-shard node. That is...very do-able, you can save yourself sometime and use a ma

Re: [akka-user] [reactive-kafka 0.9.0.1] Why is my use of reactive-kafka so slow on commit?

Hi Greg, I don't know why the performance is low in your example, but there are several problematic aspects of how you're measuring. For any benchmark on the JVM, plaese use JMH (for sbt projects, see sbt-jmh )

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

@Roland, Indeed it is an interesting discussion, I think it is what some people might call a "definition by assumption", basically (as a parallel example): we were given something that behaves like a car (we were not told that it is a car) but it behaves like it and hence we assumed and used it

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

On Fri, Apr 1, 2016 at 2:05 PM, Roland Kuhn wrote: > Hi Guido, > > I agree with your point; I’m currently leaning towards changing the > behavior of Akka Typed (which is still experimental) to be what I consider > more consistent now, but leaving untyped actors unchanged. Any objections? > That

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

Hi Guido, I agree with your point; I’m currently leaning towards changing the behavior of Akka Typed (which is still experimental) to be what I consider more consistent now, but leaving untyped actors unchanged. Any objections? Regards, Roland > 1 apr 2016 kl. 13:58 skrev Guido Medina : > >

Re: [akka-user] Akka on Android: akka.actor.ActorInitializationException

>From the failed resolution I would guess that one Flink actor tries to instantiate something JMX related which is not available on Android. -Endre On Fri, Apr 1, 2016 at 11:04 AM, Viktor Klang wrote: > Hi Luca, > > check the stack trace of the ActorInitializationException > > On Fri, Apr 1, 20

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

I'll throw you an idea, what if you add another method, say preDestroy() to match the construction of an object, here is the representation: new object successful ? -> execute preDestroy() preStart() invocation successful? -> execute postStop() but with the difference that new object and preDest

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

And the order would be: *new instance* -> *preStart()* -> *postStop()* - if started -> *preDestroy()* - if instantiated On Friday, April 1, 2016 at 1:42:16 PM UTC+1, Guido Medina wrote: > > I'll throw you an idea, what if you add another method, say preDestroy() > to match the construction of a

Re: [akka-user] [reactive-kafka 0.9.0.1] Why is my use of reactive-kafka so slow on commit?

Also, what version of streams is this? There is no reason why the stream version could not produce 6 figure numbers, so something else is going on. Have you profiled it? -Endre On Fri, Apr 1, 2016 at 1:12 PM, Viktor Klang wrote: > Hi Greg, > > I don't know why the performance is low in your exa

Re: [akka-user] Re: Akka HTTP Websockets Java with Actor

Hi Endre, thank you for the info. All, I tested this example and noticed that AnActor is instanced only ones when Router.createRoute is called. Does this mean that one instance of AnActor is used for all websocket connections (if you have multiple parallel connections)? I thought that AnActor

[akka-user] issue with receiveRecover and router

I've configured a router for one of my persistent Actor in the application.conf. for example: deployment { "/my-router" { router = round-robin-pool nr-of-instances = 2 } } >From the log, I can see both of the instance were started. [INFO] [04/01/2016 09:

[akka-user] Re: [akka-streams] Resilient to (tcp) errors source

Ok, i find a recoverWith options that can do the trick. But i also find out that recoverWith does not play well with flatMapConcat. Consider following snippet: val outgoingConnectionFlow = Http().outgoingConnection( host = *"host"* ) Source.single(HttpRequest().withUri(uri)) .viaMat(

[akka-user] Re: issue with receiveRecover and router

We redesign our application to not configure router for the persistent Actor. On Friday, April 1, 2016 at 9:29:38 AM UTC-5, Yan Pei wrote: > > I've configured a router for one of my persistent Actor in the > application.conf. > > for example: > > deployment { > > "/my-router" { >

[akka-user] ANNOUNCE: Released akka-stream-kafka 0.11-M1

We are pleased to announce the release of the first development milestone of Akka Reactive Kafka, which is an Akka Streams connector for Kafka. The project has been incorporated in the Akka github family: akka/reactive-kafka . It was originally developed by

[akka-user] Actor restart and cluster re-announce

Hey, folks. I'm doing some work to harden our cluster to unexpected failures, and I'm having trouble with an interaction between actor supervision and the cluster. We're using akka-cluster-2.3.4. My cluster follows the worker dial-in example at http://doc.akka.io/docs/akka/2.3.14/scala/clust

[akka-user] ANNOUNCE: Akka 2.4.3 released!

ANNOUNCE: Akka 2.4.3 Released Dear hakkers, we—the Akka committers—are proud to announce the third patch release of Akka 2.4. This release focused mostly on hardening and polishing of existing features. We fixed a total of 58 flaky tests or bugs, continuing towards our stretch goal of reach

Re: [akka-user] ANNOUNCE: Akka 2.4.3 released!

Yay! On Fri, Apr 1, 2016 at 6:37 PM, Konrad Malawski wrote: > ANNOUNCE: Akka 2.4.3 Released > > Dear hakkers, > > we—the Akka committers—are proud to announce the third patch release of > Akka 2.4. > > This release focused mostly on hardening and polishing of existing > features. We fixed a tota

[akka-user] Re: Actor restart and cluster re-announce

Many issues have fixed between 2.3.4 and 2.3.15 (released today), including cluster fixes. I would recommend you to update to 2.3.15, that if you can't move to 2.4.3 (also released today) HTH, Guido. On Friday, April 1, 2016 at 5:36:52 PM UTC+1, Harold Poskanzer wrote: > > Hey, folks. I'm doi

[akka-user] ANNOUNCE: Akka Stream and Http 2.0.4 released!

Dear Hakkers, we—the Akka committers—are happy to announce the fourth maintenance release of Akka Streams & HTTP 2.0 . This update addresses stability issues for those who can not upgrade to Akka 2.4.x. Fixes in this release include:

[akka-user] Re: Actor restart and cluster re-announce

About a rolling restart pattern, this thread has a nice discussion. On Friday, April 1, 2016 at 5:43:11 PM UTC+1, Guido Medina wrote: > > Many issues have fixed between 2.3.4 and 2.3.15 (released today), > including cluster fixes.

Re: [akka-user] ANNOUNCE: Akka Stream and Http 2.0.4 released!

(This release is for Akka 2.3.x series, for those on Akka 2.4 check out the latest Akka 2.4.3 release) On Fri, Apr 1, 2016 at 6:44 PM, Martynas Mickevičius < martynas.mickevic...@lightbend.com> wrote: > Dear Hakkers, > > we—the Akka committers—are happy to announce the fourth maintenance > releas

Re: [akka-user] [reactive-kafka 0.9.0.1] Why is my use of reactive-kafka so slow on commit?

It would be interesting if you could try the new 0.11-M1. It's not ready for production yet, but we would like to measure and improve performance. https://github.com/akka/reactive-kafka /Patrik fre 1 apr. 2016 kl. 14:49 skrev Endre Varga : > Also, what version of streams is this? There is no reas

Re: [akka-user] [reactive-kafka 0.9.0.1] Why is my use of reactive-kafka so slow on commit?

Using Streams 2.4.2. Streams isn't the problem. I can do a "hello world" stream w/o reactive-kafka and get 6-figure results. It's fast! -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >>

Re: [akka-user] [reactive-kafka 0.9.0.1] Why is my use of reactive-kafka so slow on commit?

Thanks for this tip--I'll check these out! I know my timing methodology is brain-damaged, but I am applying it consistently so I can still get some rough comparative scope. My current clue is the pre-M1 code's manual commit. Kafka is apparently religious (and insistent) on maintaining single-