Re: [akka-user] Consistent Dissasociation, small cluster

It looks like the dispatcher configuration *is* actually being honored. The dispatcher reported by logging is the dispatcher used by the *logger*. By instead specifically printing out the dispatcher from within the actor by using "context.dispatcher" I can see that the configuration is getting

Re: [akka-user] Consistent Dissasociation, small cluster

I am unable to get the dispatcher configuration to be applied. After running the application and noticing the problem persist, I added a tag to see the thread name in my logging lines, and notice that actors configured to use non-default dispatchers are still using the default. Even the

Re: [akka-user] Consistent Dissasociation, small cluster

I am unable to get the dispatcher configuration to be applied. After running the application and noticing the problem persist, I added a tag to see the thread name in my logging lines, and notice that actors configured to use non-default dispatchers are still using the default. Even the

Re: [akka-user] Example about cluster sharding

Ah -- sorry, I'm entirely Scala-focused... On Fri, Jan 6, 2017 at 1:14 AM, Martin Peng wrote: > Thanks Justin! > Unfortunately I forgot to mention that I need a Java example. Do you know > some? > > Best > Martin > > On Thursday, January 5, 2017 at 7:36:01 AM UTC-8, Justin du

[akka-user] Dispatcher Problem

Hello hakkers, I am getting a *repeatable* problem I do not understand with dead letters. I believe it has to do with the dispatchers being used. I have not in any explicit manner tried to select dispatcher(s). Here is a debug excerpt: * * * * * * * [DEBUG] [01/06/2017 10:26:54.526]

Re: [akka-user] Akka Artery

I guess it is all moot now that I have stripped away the defaults and only have "changes". On Saturday, 7 January 2017 01:34:27 UTC+11, Konrad Malawski wrote: > > I actually think doing it manually like this will end up being way more > confusing... > The reference.conf / application.conf

Re: [akka-user] Akka Artery

I actually think doing it manually like this will end up being way more confusing... The reference.conf / application.conf style is rather well established in Akka or Scala apps and provides minimal boilerplate. Reference is defaults "application always wins". Who "wins" is well known here and

Re: [akka-user] Akka Artery

Hi Patrik, I am aware that artery is the new remote. My query was more about having duplicate config items at the same "path" - in different conf files. In that the example conf file for artery also includes configs items at akka.actor.xxx which are also in the akka.actor.conf example conf file

Re: [akka-user] Akka Artery

Artery config belongs to akka-remote On Fri, Jan 6, 2017 at 2:44 PM, Gavin Baumanis wrote: > Hi Konrad, > > Naturally - I am aware that the defaults ARE defaults. > But for the purpose of documenting the config and providing the > alternative choices too (Which the

Re: [akka-user] Akka Artery

Hi Konrad, Naturally - I am aware that the defaults ARE defaults. But for the purpose of documenting the config and providing the alternative choices too (Which the example configs do a pretty good job of) It "seemed harmless" to literally include the default values. But I am certainly happy

Re: [akka-user] Akka Artery

"Each Akka module has a reference configuration file with the default values." So... What I have done is "literally" take the configuration examples as individual files and "included" them ALL within *application.conf* include "akka-actor.conf" include "akka-agent.conf" include

Re: [akka-user] Akka Artery

Hi Konrad, Thanks very much for the details. I am happy to use the new tech and report anything that I find, of course... The question on "Does it completely replace the initial actor conf example file" sounds a bit weird - it is the same file, artery simply has it's own configuration section:

Re: [akka-user] Akka persistent

On Fri, Jan 6, 2017 at 2:57 AM, Dai Yinhua wrote: > Hi Patrik, > > From Akka documentation, "Note that *Cluster Sharding* > > is > using snapshots, so if you use Cluster Sharding you

Re: [akka-user] Akka Artery

You may also want to track our blog, as we're publishing things about Artery internals there: http://blog.akka.io/artery/2016/12/02/streams-in-artery http://blog.akka.io/artery/2016/12/05/aeron-in-artery Those were rather light, we have some pretty advanced stuff in there which we'll want to blog

Re: [akka-user] Akka Artery

Hi Gavin, the question boils down to when you expect to hit prod. We're still working on improving stability and production-hints-on-configuring/debugging Artery. In general since this sounds like a new project I would suggest you start using Artery and provide us with feedback if something feels

[akka-user] Akka Artery

Hi Gang, I was getting started with a technology pilot and was planning on using akka clustering. I started by creating a separate conf file for akka module / section. Since it is relatively new in the development phase - we initially plan on keeping everything updated as new versions of Scala