You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Petrov (Jira)" <ji...@apache.org> on 2021/12/12 22:21:00 UTC
[jira] [Updated] (IGNITE-16106) Communication messages incorrect string deserialization on nodes running in the JVMs with different encoding.
[ https://issues.apache.org/jira/browse/IGNITE-16106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Petrov updated IGNITE-16106:
------------------------------------
Description:
DirectByteBufferStreamImpl uses String#getBytes() that use default JVM charset to serialize string message variables. As a result communication messages string serealization/deserialization may be broken for some symbols on nodes running in the JVMs with different encoding.
The possible way to fix this issue is to reject nodes with different encoding.
was:DirectByteBufferStreamImpl uses String#getBytes() that use default JVM charset to serialize string message variables. As a result communication messages string serealization/deserialization may be broken for some symbols on nodes running in the JVMs with different encoding.
> Communication messages incorrect string deserialization on nodes running in the JVMs with different encoding.
> -------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-16106
> URL: https://issues.apache.org/jira/browse/IGNITE-16106
> Project: Ignite
> Issue Type: Bug
> Reporter: Mikhail Petrov
> Priority: Major
>
> DirectByteBufferStreamImpl uses String#getBytes() that use default JVM charset to serialize string message variables. As a result communication messages string serealization/deserialization may be broken for some symbols on nodes running in the JVMs with different encoding.
> The possible way to fix this issue is to reject nodes with different encoding.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)