[ https://issues.jboss.org/browse/ISPN-8385?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8385: ------------------------------------- That is exactly what it is. Also to note this is only an issue with embedded off heap, server is perfectly fine since the serialization occurs on the client. Looking at this there are 2 possible solutions: # We could wrap the byte[] differently, thus preventing the GlobalMarshaller from occurring. Unfortunately we would then have to store an extra byte with the key and value to signify that it is a byte[] and not a serialized object. So this still has the same issue as reported. This also would then add an additional byte overhead to non byte[] entries, which when running embedded should be the most commonly used entries by far. # If we pay attention to the upcoming cache type value and if it was _application/octet-stream_ we would know the values will always have to be byte[]. This isn't doable currently though and would only work under specific configuration settings. # We could wrap the data container retrieved from the cache and automatically perform the encoding and wrapping for the user. This is probably the cleanest method, but I am not sure if we want to do this or not. [~gustavonalle] have an opinion? Virtually all of the components you can retrieve don't do this currently. Do we then have to go and change them all? Sounds nasty to me. Therefore I am saying that this -- This message was sent by Atlassian JIRA (v7.5.0#75005)