Re: [akka-user] Path to Actor changed by Akka

You are welcome lör 15 apr. 2017 kl. 20:28 skrev Joseph Mansigian < joseph.c.mansig...@gmail.com>: > You were correct in your suspicion that the destination actor was not > running at the given path. In fact it was not running at all. In > debugging I was thrown off by seeing that a print of

Re: [akka-user] Path to Actor changed by Akka

You were correct in your suspicion that the destination actor was not running at the given path. In fact it was not running at all. In debugging I was thrown off by seeing that a print of 'self.path' in the destination actor expressed a local path and I had configured a remote path to the

Re: [akka-user] akka.actor.warn-about-java-serializer-usage Warning keep coming even when Default Java Serialization is not used

Which Akka version? Perhaps you see the issue with serialize-messages=on, which we have an improvement in progress for https://github.com/akka/akka/pull/22682 Try with serialize-messages=off /Patrik lör 15 apr. 2017 kl. 19:16 skrev Ashish Soni : > Hi All , > > Below is

[akka-user] akka.actor.warn-about-java-serializer-usage Warning keep coming even when Default Java Serialization is not used

Hi All , Below is my Akk Configuration and i do not have java serialization by default but i still see the warning message , Can some one please look and let me know what i am missing akka { loglevel = WARNING extensions = ["com.romix.akka.serialization.kryo.KryoSerializationExtension$"]

[akka-user] Akka Persitence 2.4.17: asyncReadHighestSequenceNr and recovery

Persistence recovery is working in all but one of the 8 different PersistentActors in my application. I’m testing persistence recovery using dnvriend/akka-persistence-inmemory version 2.4.17.3 as my journal. I’m restarting my actors by

[akka-user] Building workflow engine using Akka

I found some old discussions [https://groups.google.com/d/msg/akka-user/eyoNs6U8tWA/EqJW1rM7-kwJ] on using Akka to build workflow engines, but not sure whether the concepts outlined there are still relevant. FWIW, the idea of modelling the data flow on Streams

Re: [akka-user] Re: Akka cluster aware router delivers messages only SOMETIMES

There is no buffer. Perhaps you send before cluster membership is established? /Patrik fre 14 apr. 2017 kl. 00:17 skrev Alexander Lukyanchikov < alexanderlukyanchi...@gmail.com>: > Small observation - messages start deliver to the "processor" node only > when I send a lot of them (like ~ 20 per

Re: [akka-user] Path to Actor changed by Akka

The problem is not some wrong translation. Are you sure that the destination actor is running at the given path? You can enable more logging: http://doc.akka.io/docs/akka/2.5/scala/logging.html#Auxiliary_remote_logging_options /Patrik fre 14 apr. 2017 kl. 15:06 skrev Joseph Mansigian <

Re: [akka-user] Akka 2.5.0 Released

> Eviction warnings will be inevitable, as Akka Http is still going to depend > on 2.4.x. However since 2.5.x is binary backwards compatible with 2.4.x, the > 2.5.0 can be used instead of 2.4.17. OK, thanks. > Also please update streams dependency to 2.5.0 so old version can be > evicted.

Re: [akka-user] Akka 2.5.0 thread pool changes

On 14/04/2017 10:13, Martynas Mickevičius wrote: JDK FJP changed spinning behaviour which changed performance characteristics for the case when there are lots of messages in flight. More info: https://github.com/akka/akka/pull/22560 Thanks. Has this been reported upstream to the JDK