Ok - I think I understand this The serialize-message = on is not a mechanism to alert about messages that get serialized. it is in fact an instruction to serialize everything and then complain if it can't be.
I think I assumed it was an instruction to report on problems with serialization with things that needed serialization. Consequently using this to attempt to track down stuff that isn't getting serialized "silently" is not going to be effective. This will cause the program to "fail" at the first attempt to send anything anywhere that can't be serialized. On Sunday, February 21, 2016 at 10:31:00 AM UTC, Tim Pigden wrote: > > Hi > As I delve further into the serialization issue, it appears that I get the > warning > > Using the default Java serializer for class ... > > > even for classes that I wouldn't expect to be serialized (messages sent > within a single actor system). Some of which I wouldn't need or want to > serialize ever > - complex object graphs with a serializable proxy equivalent > - internal message wrappers between closely coupled actors > For some of this usage I don't see locational transparency as necessary or > particularly useful. > > So does everything get serialized (or fail to get serialized) all the > time? Or does some subsystem check sample messages to see if it could > serialize them if it felt like it? > -- >>>>>>>>>> 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.
