However, messages that have to escape the JVM to reach an actor running on a different host have to undergo some form of serialization (i.e. The objects have to be converted to and from byte arrays). Akka itself uses Protocol Buffers to serialize internal messages (i.e. Cluster gossip messages). However, the serialization.

Hey All,I am building Akka persistence plugin with Apache ignite, i have a question when it comes to event tagging, if i disable java serialization, Tagged classes failed to be serialized properly, is there a way to configure specific serialization for Event Tagged or it need to be handled in the plugin itself, the GitHub for my plugin:The exception i get:2018-11-21 21:20:48 orderManagerSystem-akka.actor.default-dispatcher-27 ERROR a.p.i.journal.IgniteWriteJournal - Attempted to serialize message using Java serialization while akka.actor.allow-java-serialization was disabled. Check WARNING logs for more details.akka.serialization.DisabledJavaSerializer$JavaSerializationException: Attempted to serialize message using Java serialization while akka.actor.allow-java-serialization was disabled. Check WARNING logs for more details.2018-11-21 21:20:48 orderManagerSystem-akka.actor.default-dispatcher-11 WARN a.s.DisabledJavaSerializer - Outgoing message attempted to use Java Serialization even though akka.actor.allow-java-serialization = off was set! Message type was: class akka.persistence.journal.TaggedI have a sample application where this issue is happening for me when I use Protobuf for events serialization:A toolkit for spring boot akka persistance event sourcing starter which contains abstracted common logic for aggregate flow definition and cluster sharding plus taking benefit of spring boot echo s.
Akka Protobuf Serialization
Now I will share a working service example of how to use the event sourcing toolkit starter in practice.
Akka Protobuf Serialization Definition
- We are trying to using protobuf with Akka and serialize all Akka messages via protobuf. For Scala, we have a library called ScalaPB which help us to generate the class, which includes methods like parseFrom, toByteArray etc for serializing or deserialize our data. But, while we try to run the program, getting below exception.
- Overall, the summary is that, yes, Kryo.is. more effort than Protobuf, and there's a distinct difference of viewpoint: you have to be annotating the serialization details.somewhere., and in the case of Kryo it requires annotating your serialized classes to a significant degree.