Sorry Guys,
I'm testing an Akka-Cluster with two actor that send one to an another a 
custom message formed by two Strings and an ActorRef.
When the second actor receives the message (serialized with kryo) it just 
become unreachable.

That's the trace of the second actor:


00:35 TRACE: [kryo] Register class ID 0: int 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$IntSerializer)
00:35 TRACE: [kryo] Register class ID 1: String 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$StringSerializer)
00:35 TRACE: [kryo] Register class ID 2: float 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$FloatSerializer)
00:35 TRACE: [kryo] Register class ID 3: boolean 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$BooleanSerializer)
00:35 TRACE: [kryo] Register class ID 4: byte 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$ByteSerializer)
00:35 TRACE: [kryo] Register class ID 5: char 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$CharSerializer)
00:35 TRACE: [kryo] Register class ID 6: short 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$ShortSerializer)
00:35 TRACE: [kryo] Register class ID 7: long 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$LongSerializer)
00:35 TRACE: [kryo] Register class ID 8: double 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$DoubleSerializer)
00:35 TRACE: [kryo] Register class ID 9: void 
(com.esotericsoftware.kryo.serializers.DefaultSerializers$VoidSerializer)
00:35 TRACE: [kryo] Register class ID 10: scala.Enumeration$Val 
(com.romix.scala.serialization.kryo.EnumerationSerializer)
00:35 TRACE: [kryo] Register class ID 11: scala.Enumeration$Value 
(com.romix.scala.serialization.kryo.EnumerationSerializer)
00:35 TRACE: [kryo] Registration required: false
00:35 TRACE: [kryo] Optimize ints: true
00:35 TRACE: [kryo] Field email: class java.lang.String
00:35 TRACE: [kryo] Field customerCode: class java.lang.String
00:35 TRACE: [kryo] Field sender: class akka.actor.ActorRef
00:35 TRACE: [kryo] Register class ID 20: com.test.common.LoginRequest 
(com.esotericsoftware.kryo.serializers.FieldSerializer)
00:35 TRACE: [kryo] References: false

Thanks for any help,
Antonio



 

Il giorno venerdì 9 settembre 2016 00:24:56 UTC+2, Federico Nusymowicz ha 
scritto:
>
> 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.

Reply via email to