[jira] [Updated] (DIRECTMEMORY-129) Kryo serializer usage is not thread safe

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRECTMEMORY-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra updated DIRECTMEMORY-129:
-----------------------------------------

    Attachment: DIRECTMEMORY-129-1.patch

Patch which uses a pool of Kryo instances to perform serialization and deserialization

Changes can also be seen at Git branch [1] 

[1] https://github.com/chetanmeh/directmemory/compare/DIRECTMEMORY-129
                
> Kryo serializer usage is not thread safe
> ----------------------------------------
>
>                 Key: DIRECTMEMORY-129
>                 URL: https://issues.apache.org/jira/browse/DIRECTMEMORY-129
>             Project: Apache DirectMemory
>          Issue Type: Bug
>          Components: Serializers
>    Affects Versions: 0.1-incubating
>            Reporter: Chetan Mehrotra
>            Priority: Minor
>         Attachments: DIRECTMEMORY-129-1.patch
>
>
> KryoSerializer uses a instance level Kryo object which is accessed concurrently. As per Kryo 2.x docs [1] the Kryo object is not threadsafe. As a fix one should use a pool of Kryo instances
> [1] https://code.google.com/p/kryo/#Threading

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira