Good that you figured it out, and thanks for sharing what was wrong rather
than leaving the question open!

--
Johan
Akka Team

On Fri, Sep 9, 2016 at 2:28 AM, Federico Nusymowicz <feden...@gmail.com>
wrote:

> DERP. I was supposed to nest serializers and serialization-bindings under
> akka.actor.... ^_^;
>
>
> On Thursday, September 8, 2016 at 3:24:56 PM UTC-7, Federico Nusymowicz
> wrote:
>>
>> I've been trying to set up kryo serialization, without success. Here's my
>> first attempt:
>>
>> akka {
>>>   ...
>>>
>>>   extensions = [
>>>     "akka.cluster.pubsub.DistributedPubSub",
>>>     "com.romix.akka.serialization.kryo.KryoSerializationExtension$"
>>>   ]
>>>
>>>   actor {
>>>     ...
>>>
>>>     kryo {
>>>       type = "graph"
>>>       idstrategy = "automatic"
>>>       buffer-size = 4096
>>>       max-buffer-size = -1
>>>       use-manifests = false
>>>       post-serialization-transformations = "lz4"
>>>       kryo-trace = false
>>>       implicit-registration-logging = true
>>>
>>>       mappings {
>>>         "life.vw.client.ConciergeTracker$StatusUpdate" = 30,
>>>         "life.vw.client.Connection$Write" = 31
>>>       }
>>>     }
>>>   }
>>>
>>>   serializers {
>>>     kryo = "com.romix.akka.serialization.kryo.KryoSerializer"
>>>   }
>>>
>>>   serialization-bindings {
>>>     "life.vw.client.ConciergeTracker$StatusUpdate" = kryo
>>>     "life.vw.client.Connection$Write" = kryo
>>>   }
>>>
>>>   ...
>>> }
>>>
>>>
>>  When I ran the cluster, I kept seeing serialization warnings:
>>
>> WARN  17:42:27.913UTC akka.serialization.Serialization(akka://vw) - Using 
>> the default Java serializer for class 
>> [life.vw.client.ConciergeTracker$StatusUpdate] which is not recommended 
>> because of performance implications. Use another serializer or disable this 
>> warning using the setting 'akka.actor.warn-about-java-serializer-usage'
>>
>>
>> I've tried a few other variations, including different values for
>> "idstrategy", class names that only use "." (in place of "$"), and
>> subclassing my messages under a shared trait. None of the attempts worked.
>>
>> I even tried replacing akka-kryo-serialization with Twitter's chill. Even
>> though I followed setup instructions in detail, I kept seeing serialization
>> warnings.
>>
>> Am I missing something obvious? Is there additional setup required when
>> using serialization together with DistributedPubSub?
>>
>> Thanks in advance for your help!
>>
>> Federico
>>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/
> current/additional/faq.html
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Akka Team
Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM
Twitter: @akkateam

-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to