Exception with null message after deserialization has String message "null".

[pablonso]

fast-serialization/src/main/java/org/nustaq/serialization/serializers/FSTThrowableSerializer.java

Line 16 in e8da559

out.writeStringUTF(t.getMessage() != null ? t.getMessage() : "null");

This code converts null String message to "null".

[pablonso]

fast-serialization/src/main/java/org/nustaq/serialization/serializers/FSTThrowableSerializer.java

Line 27 in e8da559

Constructor<? extends Throwable> constructor = objectClass.getConstructor(String.class);

fast-serialization/src/main/java/org/nustaq/serialization/serializers/FSTThrowableSerializer.java

Line 28 in e8da559

Throwable t = constructor.newInstance(in.readStringUTF()); // This causes stack trace to be filled in twice but not an easy way to solve

Also wrong constructor is used (when original exception object has null message).
Using this constructor deserialized object's message field value will be "null".
Moreover - deserialization fails when extended class has no constructor with single String argument.

[pablonso]

serializer.getConfiguration().registerSerializer(Throwable.class, new FSTThrowableSerializer(), false);

workaround worked - override serializer register with alsoForAllSubclasses turned off.