[ https://issues.jboss.org/browse/JGRP-2062?page=com.atlassian.jira.plugin.... ] Cody Ebberson commented on JGRP-2062: ------------------------------------- No worries. The workaround is straightforward enough. I haven't tried it, but simply removing "PRIMITIVE_TYPES.put(String.class,TYPE_STRING);" on line 111 of Util.java might fix the issue entirely by falling back to TYPE_SERIALIZABLE. There could be a small performance impact, but I assume that would be negligible compared to network transmission, etc. The built in serialization for java.lang.String appears to be UTF-8 plus a ~7 byte header, so total transmission size would be roughly the same. If the guidance is to use manual marshalling, then you could consider deprecating the org.jgroups.Message constructors that take Object obj. That would make it explicit that the user must implement their own marshalling. As a newcomer to JGroups, the general purpose constructor looks like an obvious option. I imagine this could be a common pitfall. Thanks for taking a look! And thanks for JGroups overall, I think it's great. -- This message was sent by Atlassian JIRA (v6.4.11#64026)